-
Notifications
You must be signed in to change notification settings - Fork 29.6k
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
Configuration option to permanently turn on --preserve-symlinks #8509
Comments
you could rename your node binary to something else and then create a shell script (named |
That's a nice idea, thanks, I'll try that. |
It should be possible to add support for environment variable Just like existing variables |
That would be a nicer solution |
This would be a huge help for us too |
Add a way through environment variables to set the --preserve-symlinks flag. Any non-null value of NODE_PRESERVE_SYMLINKS will enable symlinks. Fixes: nodejs#8509
Add a way through environment variables to set the --preserve-symlinks flag. Any non-null value of NODE_PRESERVE_SYMLINKS will enable symlinks. PR-URL: #8749 Fixes: #8509 Reviewed-By: Ilkka Myller <ilkka.myller@nodefield.com> Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Ben Noordhuis <info@bnoordhuis.nl> Reviewed-By: Colin Ihrig <cjihrig@gmail.com> Reviewed-By: Anna Henningsen <anna@addaleax.net> Reviewed-By: Rich Trott <rtrott@gmail.com>
Developing packages with peer dependencies is really really hard, I lose so many hours a day trying to setup my dev environment in just the right way so it works.
I've only once managed to get the
NODE_PATH=./node_modules
workaround working, I'm not sure why it doesn't work for me, perhaps it's to do with how I configure webpack.That flag would save me when developing locally except it doesn't seem to work with webpack and browserify, is there anyway we can permanently configure it to on so we don't have to pass it as an argument for every node process? That way webpack and browserify would work with it.
The text was updated successfully, but these errors were encountered: