Usage with npm instead of yarn
See original GitHub issueWe’re trying to include react-lineage-genome-view in a react app we’re making. I’m learning npm dependencies right now, but noticed that within the JB sphere you have:
@jbrowse/plugin-config using “pluralize”: “^7.0.0”,
while most modules are using 8.0.0. “@jbrowse/plugin-data-management” is one.
I’m getting install issues with behavior of npm install vs. ci. NPM install makes a package-lock.json with this:
"@jbrowse/plugin-config": {
"version": "1.2.0",
"resolved": "https://registry.npmjs.org/@jbrowse/plugin-config/-/plugin-config-1.2.0.tgz",
"integrity": "sha512-JVH6alZFHU7/IbsB0BJveU9Nn65i9iihc3WDIcXdC0qd0NPIEirtTnSkBG9zjCqWlk9zaZ+cq2xSTs/g/oSzYA==",
"requires": {
"@material-ui/icons": "^4.9.1",
"generic-filehandle": "^2.0.1",
"pluralize": "^7.0.0",
"react-color": "^2.19.3",
"react-simple-code-editor": "0.9.3",
"react-syntax-highlighter": "^14.0.0"
}
},
"@jbrowse/plugin-data-management": {
"version": "1.2.0",
"resolved": "https://registry.npmjs.org/@jbrowse/plugin-data-management/-/plugin-data-management-1.2.0.tgz",
"integrity": "sha512-2ORB7kVKrjkPQV+9t1Xsz31KM+6NGl2ryL8LXd5ZvYV9RR1KQmJ2Cy6Rdy8QumlrHomm3c0TMceZyaUuHwketg==",
"requires": {
"@gmod/ucsc-hub": "^0.1.3",
"@material-ui/icons": "^4.9.1",
"pluralize": "^8.0.0",
"react-virtualized-auto-sizer": "^1.0.2",
"react-vtree": "^3.0.0-beta.1",
"react-window": "^1.8.6"
},
"dependencies": {
"pluralize": {
"version": "8.0.0",
"resolved": "https://registry.npmjs.org/pluralize/-/pluralize-8.0.0.tgz",
"integrity": "sha512-Nc3IT5yHzflTfbjgqWcCPpo7DaKy4FnpB0l/zCAW0Tc7jxAiuqSxHasntB3D7887LSrA93kDJ9IXovxJYxyLCA=="
}
}
},
and installs 7.0.0. npm install executes fine. when i run “npm ci”, it deletes node_modules and reinstalls from package-lock.json. For some incomprehensible reason it leave me with an empty folder for ‘pluralize’. I cannot figure out why, but this is one inconsistency I saw.
Have you seen anything like this before?
Issue Analytics
- State:
- Created 2 years ago
- Comments:5 (1 by maintainers)
Top Results From Across the Web
How to make create-react-app use npm instead of yarn?
You can either. 1) Remove yarn.lock , and running npm i ,. or. 2) Run create-react-app app --use-npm.
Read more >Migrating from npm - Yarn
Migrating from npm should be a fairly easy process for most users. Yarn can consume the same package.json format as npm, and can...
Read more >Yarn vs npm: Everything You Need to Know - SitePoint
Yarn stands for Yet Another Resource Negotiator. The Yarn package manager is an alternative to npm, released by Facebook in October 2016. The ......
Read more >Yarn vs NPM: A Comprehensive Comparison - phoenixNAP
Both tools use encryption protocols to ensure safe data transfer. Yarn verifies packages with checksum, while NPM uses SHA-512 (Secure Hash ...
Read more >NPM vs Yarn: Which package manager should I use?
As previously stated, Yarn installs dependency packages in parallel, whereas NPM installs them sequentially. As a result, Yarn outperforms NPM ...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
You should be able to add --legacy-peer-deps to the npm install command. The reason for this issue is that many react packages have peerDependency on react 16 and we are trying to use 17
Similar issue here. npm install with the following package.json can’t resolve the dependencies:
I’m using npm 7.19.1. I tried other react and jbrowse versions but the problem persists