-
-
Notifications
You must be signed in to change notification settings - Fork 6.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
.version file contains 3.0.0-beta.15
in .rc3 npm package
#1613
Comments
Yes, this bug cause the problem in CI bamboo but at the same time build on local machine works fine. |
I encountered the issue on my local machine, with a clean npm cache. |
@thetre97 This is unrelated. See #1582 (comment) |
Okay, thanks. Will delete as unrelated. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Version
3.0.0-rc.3
Reproduction link
https://unpkg.com/@vue/cli@3.0.0-rc.3/lib/util/
Steps to reproduce
npm install -g @vue/cli
@vue/cli
npm folder (on Windows\Users\{username}\AppData\Roaming\npm\node_modules\@vue\cli\lib\util
).version
file, it contains3.0.0-beta.15
What is expected?
I assume the file should contain
3.0.0-rc.3
(or whatever happens to be the latest version). And that when creating a new app, the packagedevDependencies
should be from the latest version. However, they are using the value from the.version
file, e.g.3.0.0-beta.15
.What is actually happening?
Looking at the
@vue/cli/lib/util/getVersions.js
file (https://github.com/vuejs/vue-cli/blob/dev/packages/%40vue/cli/lib/util/getVersions.js), the code appears to use that file as a version cache if the file hasn't been modified within the past 7 days.I suspect perhaps the version number in the
.version
file was a result of a bad package? If not, then thegetVersions.js
code should compare the cached version against the latest version. I'll be submitting a PR with a change to check the cached version.The text was updated successfully, but these errors were encountered: