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

Uncaught TypeError: i.createRoot is not a function #912

Closed
hktari opened this issue Apr 11, 2024 · 5 comments
Closed

Uncaught TypeError: i.createRoot is not a function #912

hktari opened this issue Apr 11, 2024 · 5 comments

Comments

@hktari
Copy link

hktari commented Apr 11, 2024

Bug report

What is the current behavior?
navigating to the admin page shows white screen. Console shows following error:

12:03:55.222 Uncaught TypeError: i.createRoot is not a function
default decap-cms-app.js:393
cms.js:21
cms.js:29
cms.js:16
decap-cms-app.js:393:85604

If the current behavior is a bug, please provide the steps to reproduce.

  1. go to README.md and click "deploy to netlify" button
  2. navigate to the /admin page of the deployed site
  3. white screen and console error is displayed

What is the expected behavior?
Expect to see a login form and no console errors from decap-cms-app.js

Other relevant information:

Node.js version: v14.15.0
NPM/Yarn version: 6.14.8
Operating System: netlify
Additional tools:
Screenshot from 2024-04-11 12-21-44

@Ys-sudo
Copy link

Ys-sudo commented Apr 12, 2024

Same issue here encountered with gatsby v4 gatsby-plugin-decap and decap-cms-app, the solution i chose was to downgrade the plugin to "gatsby-plugin-netlify": "^5.0.0", "gatsby-plugin-netlify-cms": "^6.0.0", and "netlify-cms-app": "^2.15.72", in package.json, then the cms would work as expected.

@alexmndzdev
Copy link

any other solution? instead of returning to netlify-cms which is already deprecated

@martinjagodic
Copy link
Member

The best solution would be to submit a fix for this issue as a PR. If anyone is interested and/or has questions, let us know.

@alexmndzdev
Copy link

@hktari @Ys-sudo , you only need to upgrade node version, or at least that work for me, i had version 14 too, then when i switch to 15 it works, i have already create a pull request resolving this for the repo. Thanks for the suggestion @martinjagodic

@hktari
Copy link
Author

hktari commented Apr 18, 2024

It looks like bumping node version has fixed the issue. Thank you for your support in resolving this matter !

@hktari hktari closed this as completed Apr 18, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants