search

vuejs / vuepress

📝 Minimalistic Vue-powered static site generator
https://vuepress.vuejs.org
MIT License
22.51k stars 4.76k forks source link

No matching version found for vuepress-vite@2.0.0-beta.50-pre.1. #3096

Open uwussimo opened 1 year ago

uwussimo commented 1 year ago

Bug report

While installing vuepress on vercel, it tries to find 2.0.0-beta.50-pre.1 which doesn't exist as far as I understood.

Steps to reproduce

Download the latest version of vuepress and try to deploy it somewhere

What is expected?

Simply install everything and work correctly

What is actually happening?

Screenshot 2022-11-04 at 11 15 46

Other relevant information

SaadBazaz commented 1 year ago

Definitely an issue, still exists.

andrey-helldar commented 1 year ago

Hm...

image

andrey-helldar commented 1 year ago

Fix for me:

replace

"devDependencies": {
    "@vuepress/plugin-docsearch": "^2.0.0-beta.50",
    "@vuepress/plugin-theme-data": "^2.0.0-beta.50",
    "vuepress": "^2.0.0-beta.50"
},

with

"devDependencies": {
    "@vuepress/plugin-docsearch": "2.0.0-beta.54",
    "@vuepress/plugin-theme-data": "2.0.0-beta.54",
    "vuepress": "2.0.0-beta.54"
},
bkbonner commented 1 year ago

I still see this error.

ifengshai commented 1 year ago

I have the same problem

yixiu1043 commented 1 year ago

I have the same problem

mschiavone commented 1 year ago

I upgraded to 2.0.0-beta.61 versions and am still getting this error. Is there a workaround?

Flechman commented 1 year ago

Yep, same issue here

aedart commented 1 year ago

Also experiencing this issue for 2.0.0-beta.61. Any status on when this will be fixed?... Or at least a work-around?

wildone commented 1 year ago

+1, moved to use pnpm

Phundrak commented 1 year ago

Also experiencing this issue for 2.0.0-beta.61. Any status on when this will be fixed?... Or at least a work-around?

On my side, I ran yarn and selected a version for vuepress-vite interactively. I then modified the lockfile like so:

- vuepress-vite@2.0.0-beta.50-pre.1:
+ vuepress-vite@2.0.0-beta.61:
    version "2.0.0-beta.61"
    resolved "https://registry.yarnpkg.com/vuepress-vite/-/vuepress-vite-2.0.0-beta.61.tgz#04058551e6be014e9f2dee14c5d8043b158e032d"
    integrity sha512-4mcR8XSY5b36CYkPqF80WvoeGAEjTw6Cr9bMPHrPVSjG4qqyfVpdSdyRtXD+/5aLJB7r/L60J7PI1pKTci1+3w==
    dependencies:
      "@vuepress/bundler-vite" "2.0.0-beta.61"
      "@vuepress/cli" "2.0.0-beta.61"
      "@vuepress/core" "2.0.0-beta.61"
      "@vuepress/theme-default" "2.0.0-beta.61"

  vuepress@^2.0.0-beta.61:
    version "2.0.0-beta.50-pre.1"
    resolved "https://registry.yarnpkg.com/vuepress/-/vuepress-2.0.0-beta.50-pre.1.tgz#26eec90444bb37590f29d10dd5923e75c476189f"
    integrity sha512-4Finc3GDscIqgRFAZFwa4SUm8tIFSVQIxnPIpQPW3kaM37rKylvUDkLrs2lMvoDPTAAE+Kf+v34tAFX+ZMGKUg==
    dependencies:
-     vuepress-vite "2.0.0-beta.50-pre.1"
+     vuepress-vite "2.0.0-beta.61"

Adding the yarn.lock file to the repo then enables me to reinstall everything non-interactively with a simple yarn command, which should modify the rest of the lockfile correctly.

I’m not sure how this could be done with npm, however.

ThomasHang commented 1 year ago

By running the command "yarn add -D vuepress@next", the issue can be resolved. You can see that the devDependencies have added a line "@vuepress/bundler-vite": "^2.0.0-beta.51".

j-o-sh commented 1 year ago

Just leaving this here, since it cost me some time to realize:

If you are getting this error because you tried to run npm up on your project, make sure to fix the version of vuepress in your package.json first.

"dependencies": { "vuepress": "2.0.0-beta.61" }

instead of ^2.0.0-beta.61.

The npm semver algorythm seems to get confused with beta tags and tries to upgrade to an older package, which is why you get this error then.

✌️

ChaominRuan commented 1 year ago

I had the same problem, I was using version 2.0.0-beta.51.

Changing "vuepress":"^2.0.0-beta.51" to "vuepress": "2.0.0-beta.51" solved it

Tofandel commented 1 year ago

The issue is if you are using a range for the beta version, there is an invalid 2.0.0-beta.50-pre.1. version that has been published, because semantic versionning considers it a higher version than say 2.0.0-beta.64

It's a tricky situation to fix this now unless the beta is somehow bumped to 2.0.1-beta

To avoid it for now, pin the vuepress dependency to your desired version (eg: "vuepress": "2.0.0-beta.64")