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
Seems to be working in 8.15.0 (latest) for me, even though others complain about 8.14.0
Solutions
Enforce node and npm/yarn versions in package.json
i think it's over kill, but this prevents generation of lock files that are not reproducible (we have such lock files today)
Option 1: Use yarn
Option 2: Update npm to the latest version
Clearly document the version of node and npm required
If a package is manually and entry added into package.json, then we should document this in package.json
E.g. add a section, this won't be necessary if we use yarn or if we use the latest version of npm
Problem: Currently we're unable to pin certain packages to specific versions due to a bug in the version of npm used
We rely on
overrides
section inpackage.json
to pin specific packages to particular versions8.15.0 (latest)
for me, even though others complain about8.14.0
Solutions
yarn
npm
to the latest versionIf a package is manually and entry added into
package.json
, then we should document this in package.jsonE.g. add a section, this won't be necessary if we use yarn or if we use the latest version of npm
The text was updated successfully, but these errors were encountered: