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

CNA leads to a Runtime Error - "TypeError: s.getFiberRoots is not a function" - #20752

Closed
cweekly opened this issue Jan 4, 2021 · 3 comments
Closed
Labels
bug Issue was opened via the bug report template.

Comments

@cweekly
Copy link

cweekly commented Jan 4, 2021

What version of Next.js are you using?

10.0.4

What version of Node.js are you using?

14.14.19

What browser are you using?

Chrome 87

What operating system are you using?

macOS

How are you deploying your application?

yarn dev

Describe the Bug

Standard / vanilla create-next-app --example with-typescript foo leads to an Unhandled Runtime Error:

"TypeError: s.getFiberRoots is not a function"

It's only triggered if devTools extension is enabled. Confirmed in both Chrome 87 and Firefox 84.0.1 (macOS).

Expected Behavior

DevTools should not trigger runtime errors following standard create-next-app --example with-typescript.

To Reproduce

node --version
v14.15.3
yarn --version
1.22.5

npx create-next-app --example with-typescript cna-ts
cd cna-ts
yarn dev

Note the call stack shows the error stems from the React DevTools extension:
chrome-extension://cgibknllccemdnfhfpmjhffpjfeidjga/bundles/backend.bundle.js (1:23142)
...
and sure enough, the error seems to be triggered only in browsers where React DevTools is running.

@cweekly cweekly added the bug Issue was opened via the bug report template. label Jan 4, 2021
@cweekly
Copy link
Author

cweekly commented Jan 5, 2021

UPDATE: I misspoke in blaming React DevTools -- it's actually the Reactime extension that causes this error. Closing this issue, as it's clearly a bug in Reactime and not a NextJS issue per se. Sorry for the noise -- and happy new year!

EDIT: updating to link to the Reactime issue: open-source-labs/Reactime#232

@cweekly cweekly closed this as completed Jan 5, 2021
@doug-lessen
Copy link

I had to remove or disable the Reactime plugin for my browser in order to get this error to go away.

@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 27, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Issue was opened via the bug report template.
Projects
None yet
Development

No branches or pull requests

3 participants