Gatsby: [v2] `gatsby develop` not working

Created on 13 Jul 2018 · 7Comments · Source: gatsbyjs/gatsby

Description

gatsby develop stops at the step info bootstrap finished. Everything worked fine before I did npm update on all packages. This is what changed:

Package                                Current         Wanted   Latest  Location
eslint                                  4.19.1         4.19.1    5.1.0  vo-website-2
gatsby                           2.0.0-beta.21  2.0.0-beta.32  1.9.273  vo-website-2
gatsby-plugin-feed                2.0.0-beta.3   2.0.0-beta.3   1.3.25  vo-website-2
gatsby-plugin-google-analytics    2.0.0-beta.2   2.0.0-beta.2   1.0.31  vo-website-2
gatsby-plugin-offline             2.0.0-beta.3   2.0.0-beta.3   1.0.18  vo-website-2
gatsby-plugin-react-helmet        3.0.0-beta.3   3.0.0-beta.3   2.0.11  vo-website-2
gatsby-plugin-sharp               2.0.0-beta.3   2.0.0-beta.5   1.6.48  vo-website-2
gatsby-remark-copy-linked-files   2.0.0-beta.2   2.0.0-beta.2   1.5.37  vo-website-2
gatsby-remark-images              2.0.1-beta.4   2.0.1-beta.6   1.5.67  vo-website-2
gatsby-remark-prismjs             3.0.0-beta.3   3.0.0-beta.3    2.0.4  vo-website-2
gatsby-remark-responsive-iframe   2.0.0-beta.2   2.0.0-beta.2   1.4.20  vo-website-2
gatsby-remark-smartypants         2.0.0-beta.2   2.0.0-beta.2   1.4.12  vo-website-2
gatsby-source-filesystem          2.0.1-beta.3   2.0.1-beta.3   1.5.39  vo-website-2
gatsby-transformer-remark         2.1.1-beta.2   2.1.1-beta.3   1.7.44  vo-website-2
gatsby-transformer-sharp          2.1.1-beta.3   2.1.1-beta.3   1.6.27  vo-website-2

Steps to reproduce

It happens at my personal repo, after I updated to beta 32. I was not able to reproduce in another repo. The starter default crashes in another interesting way at the same step:

info bootstrap finished - 5.237 s

error The "id" argument must be of type string. Received type object


  Error: TypeError [ERR_INVALID_ARG_TYPE]: The "id" argument must be of type string. Received type ob  ject

  - loader.js:644 Module.require
    internal/modules/cjs/loader.js:644:11

I am not sure if those two problems are related or entirely different. I just checked out the repo, npm i & npm run develop.

Environment

My repo:

  System:
    OS: macOS High Sierra 10.13.6
    CPU: x64 Intel(R) Core(TM) i7-3615QM CPU @ 2.30GHz
    Shell: 5.3 - /bin/zsh
  Binaries:
    Node: 10.5.0 - ~/.nvm/versions/node/v10.5.0/bin/node
    npm: 6.1.0 - ~/.nvm/versions/node/v10.5.0/bin/npm
  Browsers:
    Chrome: 67.0.3396.99
    Firefox: 61.0.1
    Safari: 11.1.2
  npmPackages:
    gatsby: next => 2.0.0-beta.32 
    gatsby-plugin-feed: next => 2.0.0-beta.3 
    gatsby-plugin-google-analytics: next => 2.0.0-beta.2 
    gatsby-plugin-offline: next => 2.0.0-beta.3 
    gatsby-plugin-react-helmet: next => 3.0.0-beta.3 
    gatsby-plugin-sharp: next => 2.0.0-beta.5 
    gatsby-remark-copy-linked-files: next => 2.0.0-beta.2 
    gatsby-remark-images: next => 2.0.1-beta.6 
    gatsby-remark-prismjs: next => 3.0.0-beta.3 
    gatsby-remark-responsive-iframe: next => 2.0.0-beta.2 
    gatsby-remark-smartypants: next => 2.0.0-beta.2 
    gatsby-source-filesystem: next => 2.0.1-beta.3 
    gatsby-transformer-remark: next => 2.1.1-beta.3 
    gatsby-transformer-sharp: next => 2.1.1-beta.3 
  npmGlobalPackages:
    gatsby-cli: 1.1.58

Because it also happens with the starter, here is the environment of the starter:

  [... same as above]
  npmPackages:
    gatsby: next => 2.0.0-beta.32 
    gatsby-plugin-react-helmet: next => 3.0.0-beta.3 
  npmGlobalPackages:
    gatsby-cli: 1.1.58

File contents (if changed)

Repos to test:

https://github.com/timurc/vo-website-2/tree/gatsby-develop-issue
https://github.com/gatsbyjs/gatsby-starter-default/tree/v2

Source

timurc

👍10

Most helpful comment

I have the same problem using _gatsby-starter-default#v2_ and made a temporary workaround by setting gatsby to 2.0.0-beta.29 in the package.json, then npm install.

baukevanderlaan on 13 Jul 2018

👍4

All 7 comments

I have the same problem using _gatsby-starter-default#v2_ and made a temporary workaround by setting gatsby to 2.0.0-beta.29 in the package.json, then npm install.

baukevanderlaan on 13 Jul 2018

👍4

A fix for this is merged on master but I can't publish it due to npm 2fa issues. I don't have any more time to look into this today so handing over to @pieh or @KyleAMathews.

m-allanson on 13 Jul 2018

👍2 🎉1

is there a way to see if gatsby develop works with the default project can be checked with an integration test? are you interested in having a test for this?