search

scott113341 / npm-install-version

Installs node modules to versioned or custom directories.
MIT License
56 stars 11 forks source link

update dependencies for fixing vulnerabilities #44

Open xgbuils opened 6 years ago

xgbuils commented 6 years ago

43 fix

I added npm-check dev dependency and added in test script to keep the dependencies updated.

scott-lin commented 6 years ago

@xgbuils, are you still working on this PR? I'm also interested in using npm-install-version, but would like the vulnerabilities fixed.

xgbuils commented 6 years ago

I'm not the owner of this repository. I'm waiting for a signal from @scott113341 for knowing if this repository is active. If it is, I will remove node 4 in travis-ci configuration and add node 10 to fix the CI.

I'm using npmi as alternative.

Cheers!

scott-lin commented 6 years ago

Thanks for the alternative suggestion! I was looking for one, but wasn't having success.

scott-lin commented 6 years ago

Unfortunately, npmi doesn't have the functionality I need. Would love to hear from @scott113341 about this PR.

xgbuils commented 6 years ago

Hi @scott-lin ,

Just for curiosity, what functionality you need?

scott-lin commented 6 years ago

I was unable to install multiple versions of the same package to a single destination.

So something like this,

node_modules/some/path/package-v1
node_modules/some/path/package-v2

npm-install-version makes this very simple to do. Installing multiple versions of the same package with npmi resulted in the latter installs overwriting the previous ones since you cannot specify the destination folder name.

xgbuils commented 6 years ago

Ok, I had the same problem, it's simpler with this package but is possible with npmi. I asked how to install multiple versions with npmi last week and here is the answer: npmi: installing multiple versions of the same package.

For requiring the package instance just use require with the correct installation path.

Cheers!

scott-lin commented 6 years ago

I tried the path option with npmi before, but I believe it created a node_modules folder at the path specified, which was a no go for my project. I require multiple packages in the root node_modules folder of my application, but with custom directory names.

Thanks for sharing that though. It may be helpful for others.