-
Notifications
You must be signed in to change notification settings - Fork 65
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
Struggling with NextJS (app router) #783
Labels
bug
Something isn't working
Comments
IsaccoSordo
added
the
waiting for feedback
Additional feedback is needed to address the issue
label
May 28, 2024
Hi @olliejames-xtz, we opened the following issue to the Soild team: #2175 |
IsaccoSordo
removed
the
waiting for feedback
Additional feedback is needed to address the issue
label
May 29, 2024
we are struggling with exactly the same problem 😭 its pretty intense |
we might have found a "workaround". we will further test this next week. for now i created a PR that shows what changes we've done to work around all the errors: olliejames-xtz/beacon-nextjs#1 happy to hear any thoughts on this :-) |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hey all 👋
In our kanvas projects and newer nextjs projects across the board we are often running into issues with beacon, the latest of which can be seen in this bare minimum project here:
https://github.com/olliejames-xtz/beacon-nextjs
When running yarn dev my server console is flooded with errors such as:
The connection does still seem to work in dev mode
However I've seen cases where such errors occur in production which has lead to my pages 500 erroring
Most of the time when running yarn build Its fails with this error:
Historically we've had a fair few issues with beacon, it would be great to have a working NextJS example on a new version of NextJS, I think it would help a lot of people seeing as its the most popular web framework
Feel free to fork my project above or I'd be happy to add anyone as a collaborator if you know how we can resolve this!
The text was updated successfully, but these errors were encountered: