-
-
Notifications
You must be signed in to change notification settings - Fork 134
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
Vite-ssg build error in SSR step #404
Comments
same error here. |
I solved the issue by downgrade vite packages from: "vite": "^5.2.11",
"vite-bundle-visualizer": "^1.2.1",
"vite-plugin-inspect": "^0.8.4",
"vite-plugin-pwa": "^0.20.0",
"vite-plugin-vue-devtools": "^7.1.3",
"vite-plugin-vue-layouts": "^0.11.0",
"vite-plugin-webfont-dl": "^3.9.4",
"vite-ssg": "^0.23.7",
"vite-ssg-sitemap": "^0.6.1",
"vitest": "^1.6.0", to: "vite": "5.0.3",
"vite-bundle-visualizer": "0.11.0",
"vite-plugin-inspect": "0.7.42",
"vite-plugin-pwa": "0.17.2",
"vite-plugin-vue-devtools": "1.0.0-rc.5",
"vite-plugin-vue-layouts": "0.8.0",
"vite-plugin-webfont-dl": "3.9.1",
"vite-ssg": "0.23.5",
"vite-ssg-sitemap": "0.6.1",
"vitest": "1.0.0-beta.6"
|
Thank you so much it worked! @ademtonay |
I am running into the same issue except downgrading packages is not fixing it for me. |
I also encountered the same problem, my vite version is 5.3.1。 |
I solved the problem for me by downgrading "vue3-carousel" (from 0.3.3) by adding the following dependency: "vue3-carousel": "0.3.1" |
Hey @muckch , I'm gonna try this too thanks. |
Describe the bug
I'm using vue3-carousel in my project and getting following error while building with
build
script.Reproduction
none
System Info
System: OS: macOS 14.4.1 CPU: (10) arm64 Apple M2 Pro Memory: 619.52 MB / 16.00 GB Shell: 3.6.1 - /opt/homebrew/bin/fish Binaries: Node: 20.13.1 - /opt/homebrew/opt/node@20/bin/node npm: 10.2.5 - /usr/local/bin/npm pnpm: 9.1.1 - ~/Projects/kt-dent/node_modules/.bin/pnpm Browsers: Chrome: 124.0.6367.209 Safari: 17.4.1
Used Package Manager
pnpm
Validations
Contributions
The text was updated successfully, but these errors were encountered: