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
We tried a recent round of updating npm packages in #645
However, #645 was only to update package versions that satisfy what is mentioned in package.json. That is, ^4.0.2 means npm update will only look for versions between 4.0.2 and any newer version with this format 4.x.x.
Some of packages become out-of-date very soon, for example, @wordpress/scripts(code ref) is using ^7.2.0 while its latest version is 16.1.2 (npmjs link).
From this comment #659 (comment)
Reasoning
We tried a recent round of updating npm packages in #645
However, #645 was only to update package versions that satisfy what is mentioned in package.json. That is,
^4.0.2
meansnpm update
will only look for versions between4.0.2
and any newer version with this format4.x.x
.Some of packages become out-of-date very soon, for example,
@wordpress/scripts
(code ref) is using^7.2.0
while its latest version is16.1.2
(npmjs link).@nielslange somewhat mentioned this here #645 (review)
How to do
npm
does not support this by default. Instead, we need to use another package to do that.I tried this guide https://flaviocopes.com/update-npm-dependencies/
Here is the PR and its tests (I used my repo to avoid dumping so many GitHub Actions to our main repo here):
The text was updated successfully, but these errors were encountered: