how to install multiple versions of package using npm
Due to https://github.com/npm/npm/issues/2943, npm will never support the ability to alias packages and install multiple versions of the same package.
The workarounds posted on the github issue might work for pure-JS modules, but as npm becomes a standard for frontend package management, packages now include various assets such as CSS.
Is there any workaround to install multiple versions of the same package?
The best idea I've come up with is to "clone" a package, and publish it with a slightly different name.
For example, if you need multiple versions of jquery, you could just publish packages called jquery-alias1, jquery-alias2, jquery-alias3 etc, and then set the appropriate versions in your package.json.
Or you could name the packages according to their version number, eg jquery-1.11.x, jquery-2.1.x, etc..
Both of these approaches seem sloppy though. Are there better ones?
As of npm v6.9.0, npm now supports package aliases. It implements the same syntax as Yarn uses:
npm install jquery2@npm:jquery@2
npm install jquery3@npm:jquery@3
This adds the following to package.json:
"dependencies": {
"jquery2": "npm:jquery@^2.2.4",
"jquery3": "npm:jquery@^3.4.1"
}
It is also possible to install directly from GitHub with this syntax. For example, if you want to install both the npm registry version and a GitHub fork of the package foobar:
npm install foobar
npm install foobar-fork@github:username/foobar
I wanted to post here for anyone like me that is using Yarn and landed here. It is a more or less drop-in replacement for NPM that supports aliasing out of the box:
yarn add material-ui@latest
yarn add material-ui-next@npm:material-ui@next
then
import FlatButton from 'material-ui/FlatButton'; // v0.x
import Button from 'material-ui-next/Button'; // v1.x
(credit for example goes to https://github.com/callemall/material-ui/issues/7195#issuecomment-314547601 )
It sounds like "JSPM" might be exactly the tool you're looking for. JSPM builds on top of NPM but allows you to pull packages from multiple sources (github, npm, etc). It uses the System.js universal module loader on the front end for loading modules, and "uses flat version management to download into version-suffixed folders" that are easy to reason about.
jspm.io
When you install a package with jspm you can alias that package to a particular name, which you can later require specifically in your modules.
$ jspm install jquery
... (status msgs) ...
ok Installed jquery as github:components/jquery@^2.1.4 (2.1.4)
$ jspm install [email protected]
... (status msgs) ...
ok Installed jqueryOne as github:components/[email protected] (1.11.3)
github:components/jquery 1.11.3 2.1.4
Then in your js, you can simply require(jquery) and/or require(jqueryOne) as necessary, allowing you to go back and forth as necessary.
This goes the same for any package which you'd like to use multiple versions of.
This is quite difficult to do cleanly, due to the way npm works, so I would avoid attempting to do it in production.
However, for integration testing and similar use cases, I created a package called multidep, which lets you install multiple versions of the same package and require them like so:
var multidepPackages = require('multidep')('test/multidep.json');
var jquery1 = multidepRequire('jquery', '1.11.3');
var jquery2 = multidepRequire('jquery', '2.1.4');
In my case, I need to install an newer version 7 of react-table than the version I had installed i.e. react-table version 6 globally. So we were facing the problem for new development we need to use new version table without breaking old table functionality in application so I installed both the table with different key-
Ex.
- npm install react-table-7@npm:react-table@latest - new
- npm install react-table@npm:[email protected] - old