-
-
Notifications
You must be signed in to change notification settings - Fork 2k
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
Uncaught TypeError: startTransition is not a function #3557
Comments
I have the same issue. |
Same here, any updates on this? |
Merged
The same issue when enabling preact via next config file webpack: (config, { dev, isServer }) => {
if (!dev && !isServer) {
Object.assign(config.resolve.alias, {
react: 'preact/compat',
'react-dom/test-utils': 'preact/test-utils',
'react-dom': 'preact/compat',
});
}
return config; However, I do not see this issue if I use the preact plugin - https://www.npmjs.com/package/next-plugin-preact |
I also have the same issue, using preact version |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
This is a bug related to Preact with Next.js. When an exception is throw in the render phase of a clientside rendered page the Next.JS pages/_error fails to render.
Using the latest [email protected] and [email protected] and [email protected] installed, changing the route (e.g. calling Router.replace, Router.push) will throw three errors(Local development):
To Reproduce
Steps to reproduce the behavior:
Expected behavior
The page navigates to the specified link as expected.
Notes
The same as mentioned in #3233, even if I add
pages/failing
andpages/_error
, when an exception is throw in the render phase of a client-side rendered page the Next.jspages/_error
fails to render.Possibly related: #3512, #3502, #3233, preactjs/next-plugin-preact#53
The text was updated successfully, but these errors were encountered: