nturley / netlistsvg

draws an SVG schematic from a JSON netlist

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

Node v12 doesn't resolve dependancies

shuckc opened this issue · comments

Ubuntu 21.10 node with a fresh checkout (following last commit merging #109) is unable to resolve dependencies:

$ lsb_release -a
No LSB modules are available.
Distributor ID:	Ubuntu
Description:	Ubuntu 21.10
Release:	21.10
Codename:	impish

$ node -v
v12.22.5

$ git log --oneline
d083a3c (HEAD -> master, origin/master, origin/HEAD) Update packages (#109)
5a9bd6c Update CI to node 14 (#108)
05d38f2 Update ELKjs to latest version (#106)
db7a86e Add information about installing from source and compiling ts to README (#107)
1c8c7b1 Remove generic-bus alias as it was causing issues, add some documentation on WIDTH parameter (#103)
9a44cea Multimux, tribuffer, better icons, and inout support (#102)
d928270 Caught exception so grouped SVG elements without a pin ID would not t… (#96)
...

$ npm install
npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR! 
npm ERR! While resolving: netlistsvg@1.0.2
npm ERR! Found: @types/jest@26.0.24
npm ERR! node_modules/@types/jest
npm ERR!   dev @types/jest@"^26.0.23" from the root project
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peerOptional @types/jest@"^27.0.0" from ts-jest@27.1.2
npm ERR! node_modules/ts-jest
npm ERR!   dev ts-jest@"^27.0.3" from the root project
npm ERR! 
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force, or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR! 
npm ERR! See /home/chris/.npm/eresolve-report.txt for a full report.

npm ERR! A complete log of this run can be found in:
npm ERR!     /home/chris/.npm/_logs/2021-12-22T14_07_16_216Z-debug.log

If I revert to 5a9bd6c it builds OK

Is this because "@types/jest": "^26.0.23" and "jest": "^27.0.6" should be the same version?

Ah my bad. I'll fix this soon. In the meantime you should be able to --force it and have it work fine; jest is just used for if you're running npm run test.