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
"registerPreviewStyle" error with gatsby-plugin-netlify-cms #12776
Comments
I get this too, at first I thought it had something to do with us having a custom config setup, running (note about the versions: I think your version of |
in but logging the module Likely a deeper issue behind this, like mismatching babel configurations or so … |
I haven't looked deeply into this but anecdotally i have two projects, both on |
yes, can confirm that downgrading to |
I believe this has something to do with the changes in decaporg/decap-cms#2215 Looks like the cms.js that is output by webpack during the Gatsby build process is transpiled in a way isn't compatible with the ES module config. |
I have the same issue if I use decaporg/gatsby-starter-decap-cms@0706a8f (last commit of
However, if I do not remove |
is there an easy way to reproduce it? Like a demo repo or can I reproduce it with cloning our default starter and installing those 2 plugins? |
Yes, you can reproduce with the Gatsby starter and those 2 plugins. |
I will be working on this issue with @erquhart (Shawn). We should have it all stable as soon as possible. Please downgrade the |
@bjrn you are correct, |
great to hear @talves — feel free to ping me if I can help out in any way there, be it testing or setting up examples. Using |
@kennedyrose I was able to replicate what you are seeing on v2.8.0. We made a change and published it to beta. Can you try it out for us by running |
@talves @kennedyrose I did a quick check just now, and can confirm it works in my setup with The devtools console reports the following versions in use (running dev mode):
|
@bjrn Thanks for checking. I will update when the fix release is ready. Those versions are the correct ones for the fix. |
@talves anything we can assist with or do you got this? 💪 |
@wardpeet should be all good. the proposed release of |
Here is the PR (decaporg/decap-cms#2252) for the new proposed build of NetlifyCMS that would be supporting the single instance of react (as peer) for the @wardpeet the library in that PR is what would be used by us Gatsby users who want to use the plugin for netlify cms. We should be releasing that as a beta tomorrow for testing. Just keeping you updated. If you see invariant errors from the netlify cms plugin, it will get solved once we put it in place. The new library would be put into the plugin as a peer dependency in place of the |
@bjrn working on a PR for the plugin with a new (different) peer dependency, so then you will be able to use the new OR You can also try out Thanks for the patience everyone. |
@talves, I've tested this and version 2.9 works! Thanks a bunch, hopefully we can get your other PR in too. |
Description
The latest gatsby-plugin-netlify-cms doesn't seem to work with the latest netlify-cms.
Steps to reproduce
Install gatsby-plugin-netlify-cms@3.0.0-rc.1 and netlify-cms@2.8.0 and load up the /admin/ page.
Expected result
User should see the admin page with no console errors
Actual result
A blank screen with the following error is seen when loading up the Netlify CMS admin page:
Environment
The text was updated successfully, but these errors were encountered: