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

Add installTo option #84

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

Add installTo option #84

wants to merge 1 commit into from

Conversation

ajbogh
Copy link

@ajbogh ajbogh commented Sep 2, 2018

NPM likes to delete extra directories whenever another package is installed. This means that after running npm install x you have to run npm install to get the napa packages back again. Adding an installTo option can allow a developer to install napa packages to a different directory outside of node_modules ('vendor' perhaps) and prevent npm from deleting the napa packages.

NPM likes to delete extra directories whenever another package is installed. This means that after running `npm install x` you have to run `npm install` to get the napa packages back again. Adding an installTo option can allow a developer to install napa packages to a different directory outside of node_modules ('vendor' perhaps) and prevent npm from deleting the napa packages.
@ajbogh
Copy link
Author

ajbogh commented Sep 3, 2018

In order to get Node's require() method to understand the new path, the developer would have to start the app with the NODE_PATH environment variable is set to a colon-delimited list of absolute paths including the new path. Editors would still be out of luck with intellisense, but that doesn't seem terrible.

@neilchaudhuri
Copy link

Are you merging this soon? I have discovered the need to reinstall napa packages over and over again. Not fun.

@shama
Copy link
Owner

shama commented Nov 9, 2018

I agree it's a problem but I don't think we should enable custom module directories to fix it.

@Connum
Copy link

Connum commented Mar 16, 2019

A few months have passed... Any other possible solutions in sight?

@Matt-Jensen
Copy link

Matt-Jensen commented Jan 8, 2020

I'd be interested to hear if there's a better solution than this issue. I think this approach is going to be the most likely one taken by users anyway.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants