Skip to content
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

Error after update to Nextjs 15 #81

Open
joncoronel opened this issue Oct 24, 2024 · 6 comments
Open

Error after update to Nextjs 15 #81

joncoronel opened this issue Oct 24, 2024 · 6 comments
Labels
bug Something isn't working

Comments

@joncoronel
Copy link

joncoronel commented Oct 24, 2024

Updated to Nextjs 15 and it seems openpanel breaks after the update. It seems to only occur in the turbo dev server. Does not occur in production. If I remove the --turbo from the dev server, it seems to work. Although, I did not get this error before upgrading even when using turbo before. Simply importing import { OpenPanelComponent } from "@openpanel/nextjs"; causes the following error to occur:

TypeError: 'ownKeys' on proxy: trap returned extra keys but proxy target is non-extensible
   at Reflect.ownKeys (<anonymous>)
   at Object.ownKeys (C:\Users\jonny\Documents\bentome\.next\server\edge\chunks\ssr\edge-wrapper_099f8c.js:76:47)
   at getOwnPropertyNames (<anonymous>)
   at d (C:\Users\jonny\Documents\bentome\.next\server\edge\chunks\ssr\node_modules_089e05._.js:482:76)
   at c (C:\Users\jonny\Documents\bentome\.next\server\edge\chunks\ssr\node_modules_089e05._.js:487:112)
   at <unknown> (C:\Users\jonny\Documents\bentome\.next\server\edge\chunks\ssr\edge-wrapper_099f8c.js:693:27)
   at runModuleExecutionHooks (C:\Users\jonny\Documents\bentome\.next\server\edge\chunks\ssr\edge-wrapper_099f8c.js:738:9)
   at instantiateModule (C:\Users\jonny\Documents\bentome\.next\server\edge\chunks\ssr\edge-wrapper_099f8c.js:691:9)
   at getOrInstantiateModuleFromParent (C:\Users\jonny\Documents\bentome\.next\server\edge\chunks\ssr\edge-wrapper_099f8c.js:624:12)```
   
@lindesvard
Copy link
Contributor

Thanks for the report. I'll have a look

@lindesvard lindesvard added the bug Something isn't working label Oct 28, 2024
@lindesvard
Copy link
Contributor

Just tried on a fresh installation of nextjs 15 without any issues. Can you create a reproducible repo where I can check?

@joncoronel
Copy link
Author

Okay, so tested a bit more and the error occurs when both --turbo is enabled and the root layout is set to export const runtime = "edge";.

@joncoronel
Copy link
Author

https://github.com/joncoronel/vps-testing

Also replicated here. Fresh install of next 15 and react 19.

@lindesvard
Copy link
Contributor

Great, I could reproduce the error now. Will give to solve this

@lindesvard
Copy link
Contributor

lindesvard commented Nov 15, 2024

Late on this but I know the problem. Just need to dig a bit more into this since it breaks on nextjs pages folder if I do this change. Hang in there

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants