-
-
Notifications
You must be signed in to change notification settings - Fork 6.4k
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
Maximum call stack size exceeded on use manualChunks
#2906
Labels
Comments
Same error with more simple example. manualChunks(id) {
if (id.includes('semantic-ui')) {
return 'semantic';
} else if (id.includes('react-dom')) {
return 'react';
} else if (id.includes('node_modules')) {
return 'vendor';
}
}, If I remove one condition it's working. |
If you try to split the dependencies with more than two modules, the same error always occurs |
psaren
added a commit
to psaren/vite
that referenced
this issue
Apr 10, 2021
9 tasks
psaren
added a commit
to psaren/vite
that referenced
this issue
Apr 11, 2021
psaren
added a commit
to psaren/vite
that referenced
this issue
Apr 13, 2021
psaren
added a commit
to psaren/vite
that referenced
this issue
Apr 13, 2021
psaren
added a commit
to psaren/vite
that referenced
this issue
Apr 13, 2021
psaren
added a commit
to psaren/vite
that referenced
this issue
Apr 14, 2021
psaren
added a commit
to psaren/vite
that referenced
this issue
Apr 14, 2021
psaren
added a commit
to psaren/vite
that referenced
this issue
Apr 14, 2021
patak-dev
pushed a commit
that referenced
this issue
Apr 14, 2021
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Describe the bug
When I using
manualChunks
to split node_modules dependencies into chunk files, the error[vite:build-html] Maximum call stack size exceeded
appears.This bug only occurs when the manualChunks option is present in build.rollupOptions with the settings presented in this vite.config.ts:
Reproduction
System Info
Output of
npx envinfo --system --npmPackages vite,@vitejs/plugin-vue --binaries --browsers
: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: