The npm blog has been discontinued.
Updates from the npm team are now published on the GitHub Blog and the GitHub Changelog.
Release: v7.0.0-beta.9
Heading into the holiday (in the USA at least) weekend with a fresh new npm v7 beta for you all. You can get it in the traditional way:
npm i -g npm@next-7
This adds explanatory text for ERESOLVE errors, because “unable to resolve dependency tree” was just not as helpful as we aim to be. 😅
It also adds the ability to try to do the right thing in most cases for conflicting peerDependencies when you set --force, and fixes up several other bugs reported throughout our beta process.
Thank you all for your continued help with reporting issues on the beta! We expect to have a release candidate for you soon.
v7.0.0-beta.9 (2020-09-04)
ef8f5676b#1757 view: always fetch fullMetadata, and preferOnlineac5aa709a#1758 fix scope configa36e2537foutdated: don’t throw on non-version/tag/range dep371f0f062@npmcli/arborist@0.0.20- Provide explanation objects for
ERESOLVEerrors - Support overriding certain classes of
ERESOLVEerrors with--force - Detect changes to package.json requiring package-lock dependency flag re-evaluation
- Provide explanation objects for
8e3e83bd4@npmcli/arborist@0.0.21- Remove bin links on prune
- Remove unnecessary tree walk for workspace projects
- Install workspaces on update:true
d6b134fd9#1738 #1734 fix package spec parsing during cache add process (@mjeanroy)f105eb833npm-audit-report@2.1.4:- Do not crash on cyclical meta-vulnerability references
03a9f569bopener@1.5.25616a23b4@npmcli/git@2.0.4- Support
.gitfiles, so that git worktrees are respected
- Support