Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Crashes using gatsby on missing define __MANIFEST_PLUGIN_HAS_LOCALISATION__ using gatsby-plugin-manifest
See original GitHub issueWhen using NetlifyCMS in Gatsby, and using gatsby-plugin-manifest, the admin panel crashes on the missing __MANIFEST_PLUGIN_HAS_LOCALISATION__ if statement:
https://github.com/gatsbyjs/gatsby/blob/f88a9e298261c64b3eb411ba4778ca23efd75287/packages/gatsby-plugin-manifest/src/gatsby-browser.js#L6
It gets added to gatsby here: https://github.com/gatsbyjs/gatsby/blob/f88a9e298261c64b3eb411ba4778ca23efd75287/packages/gatsby-plugin-manifest/src/gatsby-node.js#L210 The NetlifyCMS page doesn’t run via this webpack config?
Issue Analytics
- State:
- Created 4 years ago
- Comments:9 (1 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
You are correct, when I move manifest up, the CMS no longer crashes 🌈
@laurenskling thanks man, after I moved the
gatsby-plugin-netlify-cmsafter the manifest, it solved the problem.I guess, cms and netlify should be placed the last as we do not want to cache these “backend” for admin portal. The client side is what should be cached.
All good 👍