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
Don't force chokidar@2 to be downloaded from registry.npmjs.org #12182
Conversation
nicolo-ribaudo
commented
Oct 15, 2020
•
edited by gitpod-io
bot
edited by gitpod-io
bot
Q | A |
---|---|
Fixed Issues? | Fixes #12181 |
Patch: Bug Fix? | Yes |
Major: Breaking Change? | |
Minor: New Feature? | |
Tests Added + Pass? | Yes |
Documentation PR Link | |
Any Dependency Changes? | https://github.com/nicolo-ribaudo/chokidar-2 |
License | MIT |
Build successful! You can test your changes in the REPL here: https://babeljs.io/repl/build/30191/ |
This pull request is automatically built and testable in CodeSandbox. To see build info of the built libraries, click here or the icon next to each commit SHA. Latest deployment of this branch, based on commit d81a3da:
|
dbdd78d
to
d81a3da
Compare
I think the following could have worked as well: "chokidarAt2": "npm:chokidar@2.1.8" |
I think that it only works with yarn (https://docs.npmjs.com/files/package.json#dependencies does not mention it). |
Just did npm i -D chokidarAt2@npm:chokidar@2.1.8 and it worked fine. I'm on npm 6.14.8. And for extra confirmation, the package-lock.json ends up like this: "chokidarAt2": {
"version": "npm:chokidar@2.1.8",
"resolved": "https://registry.npmjs.org/chokidar/-/chokidar-2.1.8.tgz",
"integrity": "sha512-ZmZUazfOzf0Nve7duiCKD23PFSCs4JPoYyccjUFF3aQkQadqBhfzhjkwBH2mNOG9cTBwhamM37EIsIkZw3nRgg==",
"dev": true,
"requires": {
"anymatch": "^2.0.0",
"async-each": "^1.0.1",
"braces": "^2.3.2",
"fsevents": "^1.2.7",
"glob-parent": "^3.1.0",
"inherits": "^2.0.3",
"is-binary-path": "^1.0.0",
"is-glob": "^4.0.0",
"normalize-path": "^3.0.0",
"path-is-absolute": "^1.0.0",
"readdirp": "^2.2.1",
"upath": "^1.1.1"
},
"dependencies": {
... |
@nstepien The |
It doesn't work with npm 3 unfortunately:
|