List of features we want to implement

[noomorph]

Drop in your ideas what else (new/improved) you want to see?

• [x] It should work realtime with webpack-dev-server and middleware
• [ ] It should feature a web-based version and an electron version
• [ ] It'd propably also give a deeper understanding of the webpack compilation and optimization options.
• [x] It should be compatible with Webpack 1.x and 2.x
• [ ] It should be extensible (via plugins or similarly) for enthusiasts who want other ways of visualization/analysis
• [ ] It should be able to display compilation steps in a flowchart-like way, so it's visual and easy to understand sequence of build steps and transitions between them

P.S. How we'll vote for the features by the way? Anything handy in Github for that? Not sure if +1 in comments is a clean way to do it :unamused:

[sokra]

For the first error you need to use the json-loader.

The second one is here: module.paths is not supported (is not even documented in the node.js documentation and it's not good style).

I would love to have more time to maintain enhanced-require, but webpack gets more traction and eats up my whole time...

[bitplanets]

You also need to add extensions: ['', '.js', '.json'], to your webpack config. I'm also having problems on node.js... Not easy to fix.

[marr]

Interesting approach @ianbytchek. I was running into a similar issue around require.context when trying to run mocha tests on the browser. The command I ran was node node_modules/enhanced-require/bin/enhanced-require.js "mocha\!./test/index.js" and it errors with:

node node_modules/enhanced-require/bin/enhanced-require.js "mocha\!./test/index.js"

TypeError: Object #<Object> has no method 'ui'
    at Object.Mocha (/Users/dmarr/src/webpack-with-common-libs/node_modules/mocha/lib/mocha.js:83:8)
    at WEBPACK_CORE_LOADER_EXECUTION (/Users/dmarr/src/webpack-with-common-libs/node_modules/enhanced-require/node_modules/webpack-core/lib/NormalModuleMixin.js:131:71)
    at runSyncOrAsync (/Users/dmarr/src/webpack-with-common-libs/node_modules/enhanced-require/node_modules/webpack-core/lib/NormalModuleMixin.js:131:93)
    at nextLoader (/Users/dmarr/src/webpack-with-common-libs/node_modules/enhanced-require/node_modules/webpack-core/lib/NormalModuleMixin.js:233:3)
    at Storage.finished (/Users/dmarr/src/webpack-with-common-libs/node_modules/enhanced-require/node_modules/enhanced-resolve/lib/CachedInputFileSystem.js:38:16)
    at SyncNodeJsInputFileSystem.readFile (/Users/dmarr/src/webpack-with-common-libs/node_modules/enhanced-require/node_modules/enhanced-resolve/lib/SyncNodeJsInputFileSystem.js:19:4)
    at Storage.provide (/Users/dmarr/src/webpack-with-common-libs/node_modules/enhanced-require/node_modules/enhanced-resolve/lib/CachedInputFileSystem.js:56:2)
    at CachedInputFileSystem.readFile (/Users/dmarr/src/webpack-with-common-libs/node_modules/enhanced-require/node_modules/enhanced-resolve/lib/CachedInputFileSystem.js:134:24)
    at NormalModuleMixin.onLoadPitchDone (/Users/dmarr/src/webpack-with-common-libs/node_modules/enhanced-require/node_modules/webpack-core/lib/NormalModuleMixin.js:204:7)
    at NormalModuleMixin.loadPitch (/Users/dmarr/src/webpack-with-common-libs/node_modules/enhanced-require/node_modules/webpack-core/lib/NormalModuleMixin.js:157:27)

I guess this is mocha-loader's fault but i'm not certain. I filed a bug there: https://github.com/webpack/mocha-loader/issues/17