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
"@vuepress/core@1.0.0-alpha.39":
version "1.0.0-alpha.39"
"@vuepress/core@^1.0.0-alpha.39":
version "1.0.0-alpha.40"
That means, although I try to lock the version of @vuepress/core to 1.0.0-alpha.39, the vuepress cli will always use @vuepress/core@1.0.0-alpha.40.
I even tried to modify the yarn.lock manually and delete the "1.0.0-alpha.40" section, remove node_modules, then use yarn install --frozen-lockfile to install, and get the same node_modules...
So if we don't fix the packages version, it might be impossible to rollback/lock to a certain version of vuepress by yarn. (npm works well, though)
The text was updated successfully, but these errors were encountered:
Version
1.0.0-alpha.x
What is the issue
vuepress/packages/vuepress/package.json
Lines 32 to 33 in 1850be7
As shown above, we use
^
as prefix.In alpha & beta stage, it's better to lock the version without
^
.Take
@babel/core
for example:^
in release versionWhy
As known, we may have breaking changes in alpha stage, and each packages may not work well with each other if the versions are different.
When users want to rollback/lock to a certain version of vuepress, i.e.
As the dependencies of
vuepress@1.0.0-alpha.39
are:vuepress/packages/vuepress/package.json
Lines 32 to 33 in 170cf6e
They will get
1.0.0-alpha.40
for all other packages.Workaround is to lock all (possible) related packages manually:
---- update
The workaround above does not work... 😓
I got things like this:
and the
yarn.lock
file:That means, although I try to lock the version of
@vuepress/core
to1.0.0-alpha.39
, thevuepress
cli will always use@vuepress/core@1.0.0-alpha.40
.I even tried to modify the
yarn.lock
manually and delete the"1.0.0-alpha.40"
section, removenode_modules
, then useyarn install --frozen-lockfile
to install, and get the samenode_modules
...So if we don't fix the packages version, it might be impossible to rollback/lock to a certain version of vuepress by yarn. (npm works well, though)
The text was updated successfully, but these errors were encountered: