-
Notifications
You must be signed in to change notification settings - Fork 68
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
Problem when using in server side rendered page (regeneratorRuntime is not defined) #56
Comments
Got the very same problem here. Gonna look into it a bit more and see if there's any kind of sensible fix to it. Also: Bump. |
Is there any update about this? i am seeing same error on my first nuxt3 application. |
We solved it by forcing the import of the
(with the proper shim |
Same issue |
@itsmnthn I just switched the package with floating-vue |
qnp's answer solved the issue. Also, wrapping |
@valgeirb any update on this ? |
I'm using vite with vite-ssg.
|
Thank you for this conf @jbaubree. If anyone is using Nuxt 3, be sure to add these options under the vite: {
ssr: {
noExternal: ['vue3-popper'],
}
} |
Is there an official solution for this issue? I am facing the same error when working with Vue and Vitest. Installed dependencies:
At this point, the only solution I found was the one suggested by @qnp
|
stilll haooening, switching to esm file works though as stated by @qnp |
Description of the bug
Page where popper is in use does not work when server side rendered with following error:
[vite] Internal server error: regeneratorRuntime is not defined at vue3-popper@1.4.1_vue@3.2.26/node_modules/vue3-popper/dist/popper.ssr.js:1951:49
Expected behavior
Expected to work as client side rendered
Additional context
Add any other context about the problem here.
Vite + Vue3 + vite-ssr + vue3-popper@1.4.1
After doing some digging it seems like
regeneratorRuntime
is related tobabel
but that's about all I could find.The text was updated successfully, but these errors were encountered: