Report parent module filename in "Error: Cannot find module" output

[jmm]

Fix #60.

There were several tests in test/resolver.js for the Cannot find module error and I added new tests at a couple of those locations. It didn't seem like there'd be any additional value to add new tests at the other locations -- do you agree?

The next step toward exposing this in browserify will be getting browser-resolve to bump the resolve version.

[Irrelon]

Really useful to have this. Browserify "cannot find module from" error really needs this info!

[jmm]

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

[obuchtala]

Any chance that this PR gets merged?

[ljharb]

@jmm would you mind rebasing this and rerunning tests? (or checking the "allow maintainers to edit" checkbox)

[tcchau]

@ljharb @jmm It would be really nice to have this resolved. Is there anything I can do to help?

[ljharb]

@tcchau one of the two options in #64 (comment) would be ideal, so that we don't need to open a new PR.

[tcchau]

@ljharb Ah, I see, so as long as @jmm owns the PR no one else can really help this move forward unless there's a new PR created with the same changes!

[tcchau]

@ljharb I've resolved the conflicts and ensured that the tests pass in my fork of the repository after pulling from @jmm's branch. I needed the changes incorporated for a current project anyway. If you think this can help, let me know and I'll issue a PR.

[goto-bus-stop]

@tcchau if you are still interested in tackling this, opening a new PR would be great :)

[tcchau]

Hi @goto-bus-stop I will see if I can find that repo again. I've since stopped using browserify and moved on to webpack, but I'm happy to issue the PR. I need to figure what this issue was, then probably rebase with the latest and then submit. Stay tuned I guess!

[tcchau]

Hi @goto-bus-stop, I've submitted a PR #161