You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jan 20, 2022. It is now read-only.
There's really not much to say about it. Semver won't accept the dev-version no matter what
Error object
{
code: 'ERESOLVE'
current: {pkgid: 'typescript@4.0.0-dev.20200803',location: 'node_modules/typescript'}
location: '/Users/kilianhefti/dev/cmd-repo/node_modules/ts-node'
message: 'unable to resolve dependency tree'
package: 'typescript'
requiredBy: 'ts-node@8.10.2'
spec: '>=2.7'stack: 'Error: unable to resolve dependency tree // NOTE: the eval is not part of the stack of course
ateval(evalat<anonymous>(/Users/kilianhefti/.npm-packages/lib/node_modules/npm/node_modules/@npmcli/arborist/lib/arborist/build-ideal-tree.js:771:7),<anonymous>:1:15)
at Arborist.[placeDep] (/Users/kilianhefti/.npm-packages/lib/node_modules/npm/node_modules/@npmcli/arborist/lib/arborist/build-ideal-tree.js:771:7)
at /Users/kilianhefti/.npm-packages/lib/node_modules/npm/node_modules/@npmcli/arborist/lib/arborist/build-ideal-tree.js:588:4…modules/@npmcli/arborist/lib/arborist/build-ideal-tree.js:588:8)
at async Arborist.buildIdealTree (/Users/kilianhefti/.npm-packages/lib/node_modules/npm/node_modules/@npmcli/arborist/lib/arborist/build-ideal-tree.js:160:7)
at async Promise.all (index 1)
at async Arborist.reify (/Users/kilianhefti/.npm-packages/lib/node_modules/npm/node_modules/@npmcli/arborist/lib/arborist/reify.js:126:5)
at async update (/Users/kilianhefti/.npm-packages/lib/node_modules/npm/lib/update.js:34:3)'
type: 'peer'
}
The text was updated successfully, but these errors were encountered:
KilianKilmister
changed the title
[BUG] 'npm update' causes arborist to throw on unmet peer-dep in v7-beta
[BUG] (EDITED: see Companion-issues) 'npm update' causes arborist to throw on unmet peer-dep in v7-beta
Aug 17, 2020
Yeah, that's because the peer deps can't be resolved. This error is working as intended, you can npm update --legacy-peer-deps to suppress peer dep resolution.
We do need to report ERESOLVE errors better in the CLI, and Arborist needs to provide a more useful backtrace explanation object in order to do that optimally. It's second on my todo list after #113, which is a more severe failure :)
What / Why
When using
npm update
in a workspace with version mismached peer-depsHow
Current Behavior
EDIT: it's much more about the reason for the error not trickeling down properly, as only the message " unable to resolve dependency tree" is included in the output
Companion issue in npm/cli
RRFC about current peer-dep behaviour
There's really not much to say about it. Semver won't accept the dev-version no matter whatError object
The text was updated successfully, but these errors were encountered: