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
In #2545, @menghif and I are debugging an issue in CI with versions and the lock file. It led me to take a look at what packages/versions we have defined for dependencies and devDependencies in all of our package.json files (see below).
tldr;: we should standardize all of our packages, and probably start using ^ versions by default, since pnpm is going to introduce a lock file. See my Analysis section below for what needs to be found/fixed.
Looking at these, I notice that we are defining multiple versions of the same dependencies, sometimes with pinned versions, and sometimes with caret (^) versions, which will pull in newer versions if available:
We're thinking to try and see how it goes. Right now we have an odd mix of pinned and un-pinned versions, so it's a mess (see above). The lock files will help a ton in CI and deployment especially.
In #2545, @menghif and I are debugging an issue in CI with versions and the lock file. It led me to take a look at what packages/versions we have defined for
dependencies
anddevDependencies
in all of ourpackage.json
files (see below).tldr;: we should standardize all of our packages, and probably start using
^
versions by default, sincepnpm
is going to introduce a lock file. See my Analysis section below for what needs to be found/fixed.devDependencies
Dependencies
Analysis
Looking at these, I notice that we are defining multiple versions of the same dependencies, sometimes with pinned versions, and sometimes with caret (
^
) versions, which will pull in newer versions if available:The text was updated successfully, but these errors were encountered: