-
-
Notifications
You must be signed in to change notification settings - Fork 6.3k
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
SSR multi-page app build error: Multiple inputs are not supported for "output.inlineDynamicImports". #2656
Comments
I tried to add If I comment out build object from config it correctly compiles server code:
However with following config:
running
|
@ondrejrohon I'm running into the same problem. Thanks for the test repo. Does anyone know how to fix this ? |
I still haven't found any solution to this, and it unfortunately stopped me to migrate my project to Vite :( |
@ondrejrohon yeah.. I've released a plugin for Vite to do SSR, still stuck at the Muti-Page building and #2958 , looks like this feature is still not yet on ready for production. |
I encountered the same problem. So far my workaround is to have 2 vite config files: one for building the app JS and one for the SSR. The app Vite config basically inherits from the SSR and adds the different entrypoints in |
Closing as #7275 fixed #2656 (comment). |
Describe the bug
Building server for multi-page app with SSR throws this error:
Reproduction
https://github.com/ondrejrohon/vite-multipage-test
System Info
Output of
npx envinfo --system --npmPackages vite,@vitejs/plugin-vue --binaries --browsers
:System:
OS: macOS 10.15.7
CPU: (16) x64 Intel(R) Core(TM) i9-9880H CPU @ 2.30GHz
Memory: 64.46 MB / 16.00 GB
Shell: 5.7.1 - /bin/zsh
Binaries:
Node: 14.14.0 - /usr/local/bin/node
Yarn: 1.22.10 - /usr/local/bin/yarn
npm: 6.14.8 - /usr/local/bin/npm
Browsers:
Brave Browser: 89.1.21.77
Chrome: 89.0.4389.90
Firefox: 85.0.2
Safari: 14.0.3
npmPackages:
vite: ^2.1.2 => 2.1.2
Used package manager: yarn
Logs
Before submitting the issue, please make sure you do the following
The text was updated successfully, but these errors were encountered: