gatsby-starter-decap-cms: gatsby develop- does not work on unaltered clone

Bug report

What is the current behavior? unaltered clone of repo errors and build fails using “gatsby develop” (also tried npm run develop)

If the current behavior is a bug, please provide the steps to reproduce. git clone https://github.com/netlify-templates/gatsby-starter-netlify-cms.git myapp cd myapp npm install npm run develop

What is the expected behavior? running gatsby develop should not produce an error on unmodified repository clone.

Other relevant information: gatsby -v Gatsby CLI version: 2.7.2 Gatsby version: 2.10.0 nodejs -v v8.11.4 npm -v 6.9.0

System: OS: Linux 4.18 Ubuntu 18.10 (Cosmic Cuttlefish) CPU: (2) x64 Intel® Core™2 CPU 6600 @ 2.40GHz Shell: 4.4.19 - /bin/bash Binaries: Node: 11.12.0 - /usr/local/bin/node Yarn: 1.16.0 - /usr/bin/yarn npm: 6.9.0 - /usr/local/bin/npm Languages: Python: 2.7.16 - /usr/bin/python Browsers: Chrome: 75.0.3770.100 Firefox: 67.0.4 npmPackages: gatsby: ^2.1.34 => 2.10.0 gatsby-image: ^2.0.23 => 2.2.1 gatsby-plugin-netlify: ^2.0.6 => 2.1.0 gatsby-plugin-netlify-cms: ^4.0.0 => 4.1.0 gatsby-plugin-purgecss: ^4.0.0 => 4.0.0 gatsby-plugin-react-helmet: ^3.0.4 => 3.1.0 gatsby-plugin-sass: ^2.0.7 => 2.1.0 gatsby-plugin-sharp: ^2.0.15 => 2.2.1 gatsby-remark-copy-linked-files: ^2.0.7 => 2.1.0 gatsby-remark-images: ^3.0.1 => 3.1.0 gatsby-remark-relative-images: ^0.2.1 => 0.2.2 gatsby-source-filesystem: ^2.0.26 => 2.1.0 gatsby-transformer-remark: ^2.3.4 => 2.5.0 gatsby-transformer-sharp: ^2.1.9 => 2.2.0 npmGlobalPackages: gatsby-cli: 2.7.2

Node.js version: NPM/Yarn version Operating System: Additional tools:

About this issue

  • Original URL
  • State: closed
  • Created 5 years ago
  • Reactions: 1
  • Comments: 15 (7 by maintainers)

Most upvoted comments

The dependency range is fine, lockfiles just haven’t been updated - we use Renovate to do that automatically every week, but I guess 4.0.3 of the plug-in hadn’t been released last time it ran. I’ll push fresh lockfile updates in the am.

Sent with GitHawk

Fixed for now, although the CMS build is throwing an error too, need to investigate that.

Actually just realizing this should probably be fixed right away, hunting the bad commit now.