Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Browserify doesn't use $NODE_PATH to resolve transforms #1626

Open
greim opened this issue Sep 15, 2016 · 3 comments
Open

Browserify doesn't use $NODE_PATH to resolve transforms #1626

greim opened this issue Sep 15, 2016 · 3 comments

Comments

@greim
Copy link

greim commented Sep 15, 2016

This:

NODE_PATH=/some/path
browserify -t foo main.js > bundle.js

...fails when foo is resolved at /some/path. Also created a related PR here: browserify/module-deps#120 regarding cases where dependencies' transforms were failing to load for similar reasons.

@cguinnup
Copy link

cguinnup commented Nov 18, 2016

Just ran into the same issue. Thanks for the PR -- absent an integration into browserify, that code is handy to use in a custom patch, if necessary :)

@damncabbage
Copy link

Just ran into the same issue here as well. Double-thanks for the PR. 🎉

@sternenseemann
Copy link

This seems to be caused by this issue: browserify/resolve#39

Unfortunately it seems like this has been dubbed an intended behaviour although all documentation still states that NODE_PATH works. This is especially frustrating because it seems now that opts.paths can't be set from the command line.

sternenseemann added a commit to sternenseemann/browserify-handbook that referenced this issue Jul 21, 2020
browserify doesn't implicitly set opts.paths to NODE_PATH anymore
unlike stated previously in this documentation. For background see:

* browserify/resolve#39 (comment)
* browserify/resolve#47
* browserify/browserify#1626
sternenseemann added a commit to sternenseemann/browserify-handbook that referenced this issue Jul 21, 2020
browserify doesn't implicitly set opts.paths to NODE_PATH anymore
unlike stated previously in this documentation. For background see:

* browserify/resolve#39 (comment)
* browserify/resolve#47
* browserify/browserify#1626
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

4 participants