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
After updating to npm 8 workspaces, npm version-bump isn't working correctly...
Steps to reproduce
Run npm run version-bump, and update a patch version. Commit the change (don't push it)
rm -rf node_modules
npm install
Expected results
3. npm install succeeds
Actual results
3. npm install fails with an error:
➜ main git:(web-v0.11.4) npm install
npm ERR! code ETARGET
npm ERR! notarget No matching version found for @deephaven/iris-grid@^0.11.4.
npm ERR! notarget In most cases you or one of your dependencies are requesting
npm ERR! notarget a package version that doesn't exist.
npm ERR! A complete log of this run can be found in:
npm ERR! /home/bender/.npm/_logs/2022-03-25T21_54_06_342Z-debug-0.log
Additional details and attachments
It looks like the problem is because package-lock.json isn't updating??? There is a weird way to workaround this issue:
After deleting node_modules, In package.json, apply the following diff:
After running npm install, package-lock.json will be updated. Revert the change to package.json, then run npm install again. It should now work correctly after deleting node_modules again.
The text was updated successfully, but these errors were encountered:
Description
After updating to npm 8 workspaces, npm version-bump isn't working correctly...
Steps to reproduce
npm run version-bump
, and update a patch version. Commit the change (don't push it)rm -rf node_modules
npm install
Expected results
3.
npm install
succeedsActual results
3.
npm install
fails with an error:Additional details and attachments
It looks like the problem is because package-lock.json isn't updating??? There is a weird way to workaround this issue:
npm install
npm install
, package-lock.json will be updated. Revert the change topackage.json
, then runnpm install
again. It should now work correctly after deletingnode_modules
again.The text was updated successfully, but these errors were encountered: