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
Right now we are using the caret (^) version specifier in package.json for most packages. This will cause npm to use the latest minor version of a package at build time (absentpackage-lock.json). This means that packages are silently and unpredictably upgraded, leading to problems when a newer package version introduces breaking changes or bugs. Experience has taught us that both happen with unfortunate regularity.
The text was updated successfully, but these errors were encountered:
Right now we are using the caret (^) version specifier in package.json for most packages. This will cause npm to use the latest minor version of a package at build time (absent
package-lock.json
). This means that packages are silently and unpredictably upgraded, leading to problems when a newer package version introduces breaking changes or bugs. Experience has taught us that both happen with unfortunate regularity.The text was updated successfully, but these errors were encountered: