Vuepress Hope
[Bug] I am not use if it is a bug or not? I can not deploy it in vercel #4170
Answered
by
Mister-Hope
bbruceyuan
asked this question in
Q&A
-
Checklist
Package namevuepress-theme-hope Which operating system are you using?
Describe the bug
pageckage list: "devDependencies": {
"@vuepress/bundler-vite": "2.0.0-rc.9",
"@vuepress/helper": "2.0.0-rc.28",
"@vuepress/plugin-feed": "^2.0.0-rc.30",
"@vuepress/plugin-google-analytics": "^2.0.0-rc.30",
"@vuepress/plugin-redirect": "^2.0.0-rc.30",
"@vuepress/plugin-sitemap": "^2.0.0-rc.30",
"@vuepress/plugin-umami-analytics": "^2.0.0-rc.30",
"mathjax-full": "3.2.2",
"vue": "^3.4.27",
"vuepress": "2.0.0-rc.9",
"vuepress-plugin-search-pro": "2.0.0-rc.43",
"vuepress-theme-hope": "v2.0.0-rc.43"
}
name: docs
on:
# 每当 push 到 main 分支时触发部署
push:
branches: [main]
jobs:
docs:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v4
with:
# “最近更新时间” 等 git 日志相关信息，需要拉取全部提交记录
fetch-depth: 0
- name: Setup Node.js
uses: actions/setup-node@v4
with:
# 选择要使用的 node 版本
node-version: '20'
- name: Install and Build 🔧 # This example project is built using npm and outputs the result to the 'build' folder. Replace with the commands required to build your project, or remove this step entirely if your site is pre-built.
run: |
npm install --force
npm run docs:build
# 查看 workflow 的文档来获取更多信息
# @see https://github.com/crazy-max/ghaction-github-pages
- name: Deploy to GitHub Pages
uses: crazy-max/ghaction-github-pages@v2
with:
# 部署到 gh-pages 分支
target_branch: gh-pages
# 部署目录为 VuePress 的默认输出目录
build_dir: docs/.vuepress/dist
env:
# @see https://docs.github.com/cn/actions/reference/authentication-in-a-workflow#about-the-github_token-secret
GITHUB_TOKEN: ${{ secrets.VUEPRESS_TOKEN }}
situation: You can find how it works now: https://bbruceyuan-github-io-bbruceyuans-projects.vercel.app/ 
Additional contextNo response |
Beta Was this translation helpful? Give feedback.
Answered by
Mister-Hope
May 20, 2024
Replies: 5 comments 1 reply
-
|
And another question: in "vuepress-theme-hope": "v2.0.0-rc.2", https://bbruceyuan.com/post/2023 will show 404. Is that a reasonable expectation? |
Beta Was this translation helpful? Give feedback.
0 replies
-
|
I think the first one is as you may unify the helper package, beta 30 plugins are requiring a minimum requirement of beta 30 helper. We are actually not expecting users to use the helper package himself, but if he is using he should be aware of that situation. |
Beta Was this translation helpful? Give feedback.
0 replies
-
|
For the url part, we are improving our performance by converting our routes to visual routes, Which means we do not actually have any route now, So any links is now normalized to an expected format. I am opening a pr to support clean url, you may review that if you are interested in it. |
Beta Was this translation helpful? Give feedback.
0 replies
-
If I remove all configs there: {
"name": "bbruceyuan.github.io",
"version": "1.0.0",
"description": "my blog source",
"main": "index.js",
"scripts": {
"docs:dev": "vuepress dev docs",
"docs:build": "vuepress build docs"
},
"repository": {
"type": "git",
"url": "git+https://github.com/bbruceyuan/bbruceyuan.github.io.git"
},
"author": "",
"license": "ISC",
"bugs": {
"url": "https://github.com/bbruceyuan/bbruceyuan.github.io/issues"
},
"homepage": "https://github.com/bbruceyuan/bbruceyuan.github.io#readme",
"devDependencies": {
"@vuepress/bundler-vite": "2.0.0-rc.9",
"@vuepress/helper": "2.0.0-rc.28",
"@vuepress/plugin-feed": "^2.0.0-rc.30",
"@vuepress/plugin-google-analytics": "^2.0.0-rc.30",
"@vuepress/plugin-redirect": "^2.0.0-rc.30",
"@vuepress/plugin-sitemap": "^2.0.0-rc.30",
"@vuepress/plugin-umami-analytics": "^2.0.0-rc.30",
"mathjax-full": "3.2.2",
"vue": "^3.4.27",
"vuepress": "2.0.0-rc.9",
"vuepress-plugin-search-pro": "2.0.0-rc.43",
"vuepress-theme-hope": "v2.0.0-rc.43"
}
}The error messsage shows: AND JUST NOW, what I said is a wrong message. It does works in github action and vercel. The output has no body content, ALL PAGES. So is there any methods to solve it? thanks~ |
Beta Was this translation helpful? Give feedback.
0 replies
-
|
The problem is that some of the official plugins are rc30, which requires rc11 of vuepress. For now I would like to omit these kind of issue, as vuepress/core is releasing 2.0.0-rc.11, while the theme is requiring rc.9 of it. Once I align the latest version of theme with vuepress/core, you can try again and I believe the problems will be solved. Your current workaround should be reverting vuepress/core to rc9 and all official plugins to rc28, which santifies the theme requirement. |
Beta Was this translation helpful? Give feedback.
1 reply
-
|
Looking forward to the new version～ |
Beta Was this translation helpful? Give feedback.
Answer selected by
Mister-Hope
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The problem is that some of the official plugins are rc30, which requires rc11 of vuepress.
For now I would like to omit these kind of issue, as vuepress/core is releasing 2.0.0-rc.11, while the theme is requiring rc.9 of it.
Once I align the latest version of theme with vuepress/core, you can try again and I believe the problems will be solved.
Your current workaround should be reverting vuepress/core to rc9 and all official plugins to rc28, which santifies the theme requirement.