Skip to content
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

Isaacs/eresolve explanation #1761

Closed
wants to merge 3 commits into from

Conversation

isaacs
Copy link
Contributor

@isaacs isaacs commented Sep 4, 2020

When peerDependencies conflict, Arborist is now providing details of the
nodes and their reasons for inclusion on the Error object, including
whether or not this resolution error could be overridden using the
--force flag.

Print this data out in a minimal way as a warning if we override an
ERESOLVE forcefully. When the ERESOLVE causes the install to fail,
print a somewhat longer message, and save a MUCH longer full report to
the cache folder.

- Provide explanation objects for ERESOLVE errors
- Support overriding certain classes of ERESOLVE errors with --force
- Detect changes to package.json requiring package-lock dep flag
  re-evaluation
@isaacs isaacs requested a review from ruyadorno September 4, 2020 01:29
@isaacs isaacs requested a review from a team as a code owner September 4, 2020 01:29
When peerDependencies conflict, Arborist is now providing details of the
nodes and their reasons for inclusion on the Error object, including
whether or not this resolution error could be overridden using the
--force flag.

Print this data out in a minimal way as a warning if we override an
ERESOLVE forcefully.  When the ERESOLVE causes the install to fail,
print a somewhat longer message, and save a MUCH longer full report to
the cache folder.
@isaacs isaacs force-pushed the isaacs/eresolve-explanation branch from a4453cc to c0df068 Compare September 4, 2020 01:42
@darcyclarke darcyclarke added the Release 7.x work is associated with a specific npm 7 release label Sep 4, 2020
isaacs added a commit that referenced this pull request Sep 4, 2020
When peerDependencies conflict, Arborist is now providing details of the
nodes and their reasons for inclusion on the Error object, including
whether or not this resolution error could be overridden using the
--force flag.

Print this data out in a minimal way as a warning if we override an
ERESOLVE forcefully.  When the ERESOLVE causes the install to fail,
print a somewhat longer message, and save a MUCH longer full report to
the cache folder.

PR-URL: #1761
Credit: @isaacs
Close: #1761
Reviewed-by: @darcyclarke, @ruyadorno
@ruyadorno ruyadorno closed this Sep 4, 2020
@isaacs isaacs deleted the isaacs/eresolve-explanation branch October 2, 2020 21:39
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Release 7.x work is associated with a specific npm 7 release
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants