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 look at NODE_PATH environment variable? #593

Closed
zhaizhai opened this issue Jan 11, 2014 · 2 comments
Closed

browserify doesn't look at NODE_PATH environment variable? #593

zhaizhai opened this issue Jan 11, 2014 · 2 comments

Comments

@zhaizhai
Copy link

Is it true that browserify currently doesn't take into account the NODE_PATH environment variable when trying to resolve paths? If so, is there a reason for it, or would a pull request implementing it be welcome?

I have tried examples where nodejs can resolve a path based on $NODE_PATH but browserify seemingly cannot. I can give more details if it sounds like this is actually a bug.

@domenic
Copy link
Contributor

domenic commented Jan 13, 2014

Dupe of #72.

@ghost
Copy link

ghost commented Jan 13, 2014

Fixed in 3.20.0 with tests! Since node's module system is severely locked down the behavior of $NODE_PATH probably won't ever change.

@ghost ghost closed this as completed Jan 13, 2014
This issue was closed.
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

2 participants