Some old import from @vuepress/client and @vuepress/utils not work #1486
-
DescriptionI updated from 2.0.0-beta.177 to the latest version and encountered problems with path (import { path } from '@vuepress/utils';) and usePageFrontmatter (import { usePageFrontmatter } from "@vuepress/ client";) are introduced and used for issues. Reproductionhttps://github.com/TCA-Arknights/aneot-1.3Alpha Used Package Managerpnpm System InfoSystem:
OS: Windows 11 10.0.22631
CPU: (8) x64 11th Gen Intel(R) Core(TM) i5-11300H @ 3.10GHz
Memory: 5.02 GB / 23.79 GB
Binaries:
Node: 18.17.0 - C:\Program Files\nodejs\node.EXE
Yarn: 1.22.19 - ~\AppData\Roaming\npm\yarn.CMD
npm: 9.8.1 - C:\Program Files\nodejs\npm.CMD
pnpm: 8.6.12 - ~\AppData\Roaming\npm\pnpm.CMD
bun: Not Found
Utilities:
Git: 2.41.0.
Browsers:
Chrome: Not Found
Edge: Chromium (121.0.2277.98)
npmPackages:
@vuepress/bundler-vite: 2.0.0-rc.2 => 2.0.0-rc.2
@vuepress/bundler-webpack: Not Found
@vuepress/cli: Not Found
@vuepress/client: Not Found
@vuepress/core: Not Found
@vuepress/markdown: Not Found
@vuepress/shared: Not Found
@vuepress/utils: Not Found
vue: ^3.4.15 => 3.4.15
vue-router: Not Found
vuepress: 2.0.0-rc.2 => 2.0.0-rc.2 |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 6 replies
-
Just use Provide a minimal reproduction describing your challenge while upgrading helps me to give the correct suggestions. I don't want to dig into a whole project. Just create a new project with |
Beta Was this translation helpful? Give feedback.
add that. it is clearly.mentioned in.docs that alias requires opt-in for performance consideration