Error message should indicate which file triggered the error

[cowwoc]

I am getting this error message when running browserify:

Cannot find module 'domReady' from 'C:\Users\Gili\Documents\foo\frontend\src\main\webapp\com\foo\frontend\page'

Meaning, if file X invokes require('domReady') while fails to resolve, I am expecting the error message to contain the absolute path to X. Otherwise, these errors are very difficult to resolve (since domReady is referenced many times by different files).

[jmm]

See browserify/resolve/issues/60 and browserify/resolve/pull/64.

[cowwoc]

@jmm If this is fixed in node-resolve, will it magically get fixed in node-browserify as well (meaning, is the latter built on top of the former)? Or do you need to fix this separately?

[jmm]

These are the steps:

• [X] get node-browser-resolve to pass through opts to node-resolve
• [ ] get Report parent module filename in "Error: Cannot find module" output resolve#64 merged and pushed to npm
• [ ] get node-browser-resolve to bump node-resolve version
• [ ] get browserify to bump node-browser-resolve version

[cowwoc]

Got it. Thanks for the clarification :)

[jmm]

No problem!

[jmm]

Made a plugin for this: https://www.npmjs.com/package/browserify-require-not-found-parent

[A-312]

• [ ] get browserify/resolve#64 merged and pushed to npm

64 is browserify/resolve#162, and is merged :)

[goto-bus-stop]

I believe this is finally done in 16.5.2 😄