You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If the issue is related to 1.x -> 2.0 upgrade, read the Migration Guide first.
Describe the bug
The vite bundler throw RangeError when file is saved.
(node:5885) UnhandledPromiseRejectionWarning: RangeError: Maximum call stack size exceeded
at path/node_modules/vite/dist/node/chunks/dep-6c35d66c.js:60663:41
at Set.forEach (<anonymous>)
at invalidateSSRModule (path/node_modules/vite/dist/node/chunks/dep-6c35d66c.js:60663:19)
at path/node_modules/vite/dist/node/chunks/dep-6c35d66c.js:60663:41
at Set.forEach (<anonymous>)
at invalidateSSRModule (path/node_modules/vite/dist/node/chunks/dep-6c35d66c.js:60663:19)
at path/node_modules/vite/dist/node/chunks/dep-6c35d66c.js:60663:41
at Set.forEach (<anonymous>)
at invalidateSSRModule (path/node_modules/vite/dist/node/chunks/dep-6c35d66c.js:60663:19)
at path/node_modules/vite/dist/node/chunks/dep-6c35d66c.js:60663:41
(Use `node --trace-warnings ...` to show where the warning was created)
(node:5885) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 1)
(node:5885) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.
Reproduction
I'm not sure what to reproduce, it happens after upgrading to 2.0.0-beta.32, downgrading to beta.31 solve the issue.
Describe the bug
The vite bundler throw RangeError when file is saved.
Reproduction
I'm not sure what to reproduce, it happens after upgrading to
2.0.0-beta.32
, downgrading to beta.31 solve the issue.System Info
vite
version: 2.0.0-beta.32Logs (Optional if provided reproduction)
vite
orvite build
with the--debug
flag.The text was updated successfully, but these errors were encountered: