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

NextJS Error [Firefox] #8368

Closed
Matelasse opened this issue Aug 14, 2019 · 3 comments · May be fixed by NOUIY/next.js#353, NOUIY/next.js#369, NOUIY/next.js#408 or NOUIY/next.js#422
Closed

NextJS Error [Firefox] #8368

Matelasse opened this issue Aug 14, 2019 · 3 comments · May be fixed by NOUIY/next.js#353, NOUIY/next.js#369, NOUIY/next.js#408 or NOUIY/next.js#422
Milestone

Comments

@Matelasse
Copy link

Bug report

Describe the bug

This started happening out of the blue. I am version controlling my project, and rolling back to previous commits that worked 100% still reveals the same error when accessed by Firefox

To Reproduce

Steps to reproduce the behavior, please provide code snippets or a repository:

  1. Start dev server
  2. Chrome works fine, but use Firefox to go to your project
  3. Get these errors
The above error occurred in one of your React components:

Consider adding an error boundary to your tree to customize error handling behavior.
Visit https://fb.me/react-error-boundaries to learn more about error boundaries.

and

SyntaxError: An invalid or illegal string was specified main.js:8757
    NextJS 11
    commitRootImpl self-hosted:1102
    NextJS 3
    commitRoot self-hosted:1047
    NextJS 40

Expected behavior

This was not happening, and I don't understand why this became an issue with Firefox only and not chrome.

Screenshots

pic

System information

  • Linux
  • Firefox
  • Version of Next.js: "^9.0.4-canary.3"
@Timer Timer added this to the 9.0.4 milestone Aug 14, 2019
@mottox2
Copy link
Contributor

mottox2 commented Aug 14, 2019

I think this is same problem as #8347

firefox console results:
スクリーンショット 2019-08-15 1 13 47

@Timer
Copy link
Member

Timer commented Aug 14, 2019

Yup, this is fixed. We'll release a new canary right now!

@Timer Timer closed this as completed Aug 14, 2019
@balazsorban44
Copy link
Member

This issue has been automatically locked due to no recent activity. If you are running into a similar issue, please create a new issue with the steps to reproduce. Thank you.

@vercel vercel locked as resolved and limited conversation to collaborators Jan 31, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.