Error displayed when using dynamic composition (but everything works properly)

[aaronroberson]

I'm submitting a bug report

• Library Version:
  @easy-webpack/config-aurelia 2.0.1
• Operating System:
  OSX 10.x
• Node Version:
  4.3.2
• NPM Version:
  3.9.2
• Webpack AND Version
  webpack 2.1.0-beta.17
• Browser:
  Chrome
• Language:
  ESNext

Current behavior:

I’m getting errors when using dynamic composition:

Unable to resolve components/cs-${card.subType}-preview/cs-${card.subType}-preview

The HTML code looks like this:

<compose view-model="components/cs-${card.subType}-preview/cs-${card.subType}-preview" model.bind="card"></compose>

Expected/desired behavior:

The custom component that is dynamically included in the page should remain dynamic and not be parsed by webpack.

[niieani]

This is a valid bug, but doesn't cause any misbehavior if you specify all build resources manually.
It only causes erroneous information to be displayed.

[aaronroberson]

Gotcha! I'll leave this here as a placeholder for or anyone else to create a PR to update the logging.

[aaronroberson]

@niieani Should I also be ignoring the following output:

ERROR in ./~/fsevents/~/node-pre-gyp/lib/util/compile.js
Module not found: Error: Can't resolve 'child_process' in '/Users/arob35/Sites/nike/ashpod/node_modules/fsevents/node_modules/node-pre-gyp/lib/util'
 @ ./~/fsevents/~/node-pre-gyp/lib/util/compile.js 9:9-33
 @ ./~/fsevents/~/node-pre-gyp/lib ^\.\/.*$
 @ ./~/fsevents/~/node-pre-gyp/lib/node-pre-gyp.js
 @ ./~/fsevents/fsevents.js
 @ ./~/chokidar/lib/fsevents-handler.js
 @ ./~/chokidar/index.js
 @ ./~/nodemon/lib/monitor/watch.js
 @ ./~/nodemon/lib/monitor/index.js
 @ ./~/nodemon/lib/nodemon.js
 @ ./src ^\.\/.*$
 @ ./~/aurelia-loader-webpack/dist/commonjs/aurelia-loader-webpack.js
 @ multi aurelia

ERROR in ./~/npm/bin/npm-cli.js
Module parse failed: /Users/arob35/Sites/nike/ashpod/node_modules/npm/bin/npm-cli.js Unexpected character '#' (1:0)
You may need an appropriate loader to handle this file type.
| #!/usr/bin/env node
| ;(function () { // wrapper in case we're in module_context mode
| 
 @ ./~/npm/lib/npm.js 473:2-30
 @ ./~/fsevents/~/node-pre-gyp/lib/util/compile.js
 @ ./~/fsevents/~/node-pre-gyp/lib ^\.\/.*$
 @ ./~/fsevents/~/node-pre-gyp/lib/node-pre-gyp.js
 @ ./~/fsevents/fsevents.js
 @ ./~/chokidar/lib/fsevents-handler.js
 @ ./~/chokidar/index.js
 @ ./~/nodemon/lib/monitor/watch.js
 @ ./~/nodemon/lib/monitor/index.js
 @ ./~/nodemon/lib/nodemon.js
 @ ./src ^\.\/.*$
 @ ./~/aurelia-loader-webpack/dist/commonjs/aurelia-loader-webpack.js
 @ multi aurelia

ERROR in ./~/fsevents/~/uid-number/uid-number.js
Module not found: Error: Can't resolve 'child_process' in '/Users/arob35/Sites/nike/ashpod/node_modules/fsevents/node_modules/uid-number'
 @ ./~/fsevents/~/uid-number/uid-number.js 9:20-44
 @ ./~/fsevents/~/tar-pack/index.js
 @ ./~/fsevents/~/node-pre-gyp/lib/package.js
 @ ./~/fsevents/~/node-pre-gyp/lib ^\.\/.*$
 @ ./~/fsevents/~/node-pre-gyp/lib/node-pre-gyp.js
 @ ./~/fsevents/fsevents.js
 @ ./~/chokidar/lib/fsevents-handler.js
 @ ./~/chokidar/index.js
 @ ./~/nodemon/lib/monitor/watch.js
 @ ./~/nodemon/lib/monitor/index.js
 @ ./~/nodemon/lib/nodemon.js
 @ ./src ^\.\/.*$
 @ ./~/aurelia-loader-webpack/dist/commonjs/aurelia-loader-webpack.js
 @ multi aurelia

ERROR in ./~/npm/lib/utils/git.js
Module not found: Error: Can't resolve 'child_process' in '/Users/arob35/Sites/nike/ashpod/node_modules/npm/lib/utils'
 @ ./~/npm/lib/utils/git.js 8:11-35
 @ ./~/npm/lib ^\.\/.*\.js$
 @ ./~/npm/lib/npm.js
 @ ./~/fsevents/~/node-pre-gyp/lib/util/compile.js
 @ ./~/fsevents/~/node-pre-gyp/lib ^\.\/.*$
 @ ./~/fsevents/~/node-pre-gyp/lib/node-pre-gyp.js
 @ ./~/fsevents/fsevents.js
 @ ./~/chokidar/lib/fsevents-handler.js
 @ ./~/chokidar/index.js
 @ ./~/nodemon/lib/monitor/watch.js
 @ ./~/nodemon/lib/monitor/index.js
 @ ./~/nodemon/lib/nodemon.js
 @ ./src ^\.\/.*$
 @ ./~/aurelia-loader-webpack/dist/commonjs/aurelia-loader-webpack.js
 @ multi aurelia

[niieani]

No, this seems like an error of another kind, related to your dependencies.

As for the topic of this issue, I'll fix this either by ignoring ${...} or by resolving to a glob pattern, where * replaces any ${...} unless ${...} is the only thing there.

[EisenbergEffect]

@niieani Can this be closed?

[niieani]

No, this has not been fixed yet. I'm keeping tabs on the issues on all the webpack repos.
It's not a serious issue though, it's only an incorrectly displayed error.