gatsby-plugin-netlify-cms converting circular structure to JSON
See original GitHub issueDescription
I am migrating a Gatsby page from v2 to v3. In my project I am using gatsby-plugin-netlify-cms together with netlify-cms-app both on newest version. Locally gatsby develop and gatsby build are working perfectly. I am facing no problems at all, but when it comes to running within a pipeline on gitlab I am running into an error. I have already run gatsby clean without any effect. Also I deactivated the cache within the pipeline. If I remove gatsby-plugin-netlify-cms from gatsy-config.js the build process succeeds also on CI. NPM and NODE are running on the same versions in both environments.
Steps to reproduce
- Add
gatsby-plugin-netlify-cmstogether withnetlify-cms-appto package.json - Import
gatsby-plugin-netlify-cmsin gatsy-config.js - Run
gatsby buildlocally and on CI.
Expected result
gatsby build should succeed on pipeline like it does locally.
Actual result
gatsby build fails with the error shown in the screenshot above.
Environment
System:
OS: Linux 4.19 Debian GNU/Linux 9 (stretch) 9 (stretch)
CPU: (1) x64 Intel(R) Xeon(R) CPU @ 2.30GHz
Shell: 4.4.12 - /bin/bash
Binaries:
Node: 12.22.1 - /usr/local/bin/node
Yarn: 1.22.5 - /usr/local/bin/yarn
npm: 6.14.12 - /usr/local/bin/npm
Languages:
Python: 2.7.13 - /usr/bin/python
npmPackages:
gatsby: 3.4.1 => 3.4.1
gatsby-image: 3.4.0 => 3.4.0
gatsby-plugin-gdpr-cookies: 2.0.0 => 2.0.0
gatsby-plugin-json-remark: 1.1.5 => 1.1.5
gatsby-plugin-manifest: 3.4.0 => 3.4.0
gatsby-plugin-netlify-cms: 5.4.1 => 5.4.1
gatsby-plugin-react-helmet: 4.4.0 => 4.4.0
gatsby-plugin-react-svg: 3.0.1 => 3.0.1
gatsby-plugin-remove-serviceworker: 1.0.0 => 1.0.0
gatsby-plugin-robots-txt: 1.5.6 => 1.5.6
gatsby-plugin-s3: 0.3.8 => 0.3.8
gatsby-plugin-sharp: 3.4.1 => 3.4.1
gatsby-plugin-sitemap: 2.12.0 => 2.12.0
gatsby-plugin-styled-components: 4.4.0 => 4.4.0
gatsby-remark-custom-blocks: 3.4.0 => 3.4.0
gatsby-remark-images: 5.1.0 => 5.1.0
gatsby-source-filesystem: 3.4.0 => 3.4.0
gatsby-source-graphql: 3.4.0 => 3.4.0
gatsby-transformer-json: 3.4.0 => 3.4.0
gatsby-transformer-remark: 4.1.0 => 4.1.0
gatsby-transformer-remark-frontmatter: 1.0.1 => 1.0.1
gatsby-transformer-sharp: 3.4.0 => 3.4.0
Issue Analytics
- State:
- Created 2 years ago
- Reactions:2
- Comments:10 (2 by maintainers)
Top Results From Across the Web
gatsby-plugin-netlify-cms-paths-json
A gatsby plugin to change file paths in your markdown files to Gatsby-friendly paths when using Netlify CMS to edit them. Installation. With...
Read more >gatsby - gatsbyjs, reactjs - error when changing image (logo
The "gatsby-plugin-netlify-cms" plugin is throwing an error because it expects a file to be somewhere in the netlify cms.
Read more >How to customize a Gatsby Netlify CMS starter
In this post we'll build upon a website which uses Gatsby for the end user facing part of the website and NetlifyCMS for...
Read more >Converting Circular Structure to JSON - Career Karma
On Career Karma, learn about the restrictions of JSON in the debugging tutorial for converting circular structure to json.
Read more >gatsbyjs, reactjs - error when changing image (...anycodings
Use the basic gatsby starter from the tutorial · Change the image there, test if publish to netlify is successful · add the...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found

@LekoArts same problem here! I created a minimal reproduction repo here >https://gitlab.com/flo_kas/bug-repro<, as you can see, my build job is also failing with the same error >https://gitlab.com/flo_kas/bug-repro/-/jobs/1247734074<
Hey again!
It’s been 60 days since anything happened on this issue, so our friendly neighborhood robot (that’s me!) is going to close it. Please keep in mind that I’m only a robot, so if I’ve closed this issue in error, I’m
HUMAN_EMOTION_SORRY. Please feel free to comment on this issue or create a new one if you need anything else. As a friendly reminder: the best way to see this issue, or any other, fixed is to open a Pull Request. Check out gatsby.dev/contribute for more information about opening PRs, triaging issues, and contributing!Thanks again for being part of the Gatsby community! 💪💜