[Bug report] Cannot install any more on beta-58

[digital-codes]

Description

After the latest new beta updates I cannot get a working installation any more. I have a test project with many things here: https://github.com/digital-codes/vp2 which I constantly updated from beta 39 or so. I is up-to-date with beta-56 since a few days.

Now , when I try to got to beta-58 I get

[kugel@tux2 vp2-58]$ ./node_modules/.bin/vuepress dev docs
✔ Initializing and preparing data - done in 72ms

  vite v4.0.0 dev server running at:

  ➜  Local:   http://localhost:8080/
  ➜  Network: http://192.168.178.29:8080/
Failed to load url /home/kugel/temp/js/vp2-58/docs/.vuepress/.temp/internal/layoutComponents (resolved id: /home/kugel/temp/js/vp2-58/docs/.vuepress/.temp/internal/layoutComponents). Does the file exist?

which is like Paul mentioned in https://github.com/vuepress/vuepress-next/issues/1193 However, I cannot solve it with cleaning and fresh installation.

I cannot even run "npm update" after a completely fresh installation with veupress@next alone. It says:

kugel@tux2 vp2-58]$ npm update
npm ERR! code ETARGET
npm ERR! notarget No matching version found for vuepress-vite@2.0.0-beta.50-pre.1.

What' event more strange - my project above hast a package-lock.json which references only -beta.56 packages as dependencies. When I check it out now and run npm -i , the dependencies are changed to -beta.50-pre.1

I don't know well enough how the npm repository work, but to me it looks like there is some outdated version (beta50-pre.1) at npmjs which prevents me from getting ahead.

Any ideas what I could be doing wrong?

(Pls note, the repo above complains about a leaflet css issue which need manual fix after installation ... this is not related to the problem)

Reproduction

https://github.com/digital-codes/vp2

Used Package Manager

npm

System Info

[kugel@tux2 vp2-58]$ ./node_modules/.bin/vuepress info

  System:
    OS: Linux 6.0 Fedora Linux 36 (MATE-Compiz)
    CPU: (12) x64 Intel(R) Core(TM) i7-10710U CPU @ 1.10GHz
    Memory: 24.04 GB / 31.06 GB
    Shell: 5.2.9 - /bin/bash
  Binaries:
    Node: 16.18.1 - /usr/bin/node
    Yarn: 1.22.17 - /usr/bin/yarn
    npm: 8.19.2 - /usr/bin/npm
  Utilities:
    Git: 2.38.1 - /usr/bin/git
  Browsers:
    Chrome: Not Found
    Firefox: 107.0.1
  npmPackages:
    @vuepress/bundler-vite:  2.0.0-beta.58 
    @vuepress/bundler-webpack: Not Found
    @vuepress/cli:  2.0.0-beta.58 
    @vuepress/client:  2.0.0-beta.50-pre.1 (2.0.0-beta.58)
    @vuepress/core:  2.0.0-beta.58 
    @vuepress/markdown:  2.0.0-beta.58 
    @vuepress/plugin-active-header-links:  2.0.0-beta.58 
    @vuepress/plugin-back-to-top:  2.0.0-beta.58 
    @vuepress/plugin-container:  2.0.0-beta.58 
    @vuepress/plugin-docsearch: Not Found
    @vuepress/plugin-external-link-icon:  2.0.0-beta.58 
    @vuepress/plugin-git:  2.0.0-beta.58 
    @vuepress/plugin-google-analytics: Not Found
    @vuepress/plugin-medium-zoom:  2.0.0-beta.58 
    @vuepress/plugin-nprogress:  2.0.0-beta.58 
    @vuepress/plugin-palette:  2.0.0-beta.58 
    @vuepress/plugin-prismjs:  2.0.0-beta.58 
    @vuepress/plugin-pwa: Not Found
    @vuepress/plugin-pwa-popup: Not Found
    @vuepress/plugin-register-components: Not Found
    @vuepress/plugin-search: Not Found
    @vuepress/plugin-shiki: Not Found
    @vuepress/plugin-theme-data:  2.0.0-beta.58 
    @vuepress/plugin-toc: Not Found
    @vuepress/shared:  2.0.0-beta.50-pre.1 (2.0.0-beta.58)
    @vuepress/theme-default:  2.0.0-beta.58 
    @vuepress/utils:  2.0.0-beta.58 
    vue:  3.2.45 
    vue-loader: Not Found
    vue-router:  4.1.6 
    vuepress: ^2.0.0-beta.58 => 2.0.0-beta.58 
    vuepress-vite:  2.0.0-beta.58 
    vuepress-webpack: Not Found

[Mister-Hope]

Remove ^

[digital-codes]

Ha, that was a simple fix. Thanks a lot! Didn't know the little caret can mess up things sol badly ... Btw, to me, vuepress looks pretty useful and complete by now. Wouldn't it be time for a release candidate towards leaving beta? Or what's still missing on your roadmap?

[Mister-Hope]

At lease we have to wait #1052, also some improvements on preload and prefetch links shall be made.

Those may introduce breaking changes.