gatsby: Unknown option: .reactRuntime

Description

Running gatsby develop results in 2 errors stating: “Unknown option: .reactRuntime”

It might be something to do with images, as I noticed the errors crop up just after the console statement: “Generating image thumbnails”…

success createPages - 16.044s
success Checking for changed pages - 0.002s
success createPagesStatefully - 0.102s
success update schema - 0.116s
success write out redirect data - 0.002s
success Build manifest and related icons - 0.117s
success onPostBootstrap - 0.127s
info bootstrap finished - 77.267s
success onPreExtractQueries - 0.003s
success extract queries from components - 0.406s
success write out requires - 0.046s
success run static queries - 0.212s - 1/1 4.72/s
success run page queries - 1.786s - 1679/1679 940.12/s
success Generating image thumbnails - 4.130s - 6/6 1.45/s

 ERROR #98123  WEBPACK

Generating development JavaScript bundle failed

Unknown option: .reactRuntime. Check out https://babeljs.io/docs/en/babel-core/#options for more information about options.

File: .cache/polyfill-entry.js


 ERROR #98123  WEBPACK

Generating development JavaScript bundle failed

Unknown option: .reactRuntime. Check out https://babeljs.io/docs/en/babel-core/#options for more information about options.

File: .cache/app.js

failed Building development bundle - 0.747s

Steps to reproduce

Install the dependencies as shown and the same errors should occur.

Expected result

Project should build successfully.

Actual result

ERROR #98123  WEBPACK

Generating development JavaScript bundle failed

Unknown option: .reactRuntime. Check out https://babeljs.io/docs/en/babel-core/#options for more information about options.

File: .cache/app.js


 ERROR #98123  WEBPACK

Generating development JavaScript bundle failed

Unknown option: .reactRuntime. Check out https://babeljs.io/docs/en/babel-core/#options for more information about options.

File: .cache/polyfill-entry.js

Environment

  System:
    OS: macOS 10.15.5
    CPU: (8) x64 Intel(R) Core(TM) i7-7700HQ CPU @ 2.80GHz
    Shell: 5.7.1 - /bin/zsh
  Binaries:
    Node: 12.18.3 - /usr/local/bin/node
    Yarn: 1.21.1 - /usr/local/bin/yarn
    npm: 6.14.6 - /usr/local/bin/npm
  Languages:
    Python: 2.7.16 - /usr/bin/python
  Browsers:
    Chrome: 84.0.4147.135
    Firefox: 78.0.2
    Safari: 13.1.1
  npmPackages:
    gatsby: ^2.24.53 => 2.24.53
    gatsby-image: ^2.4.16 => 2.4.16
    gatsby-plugin-manifest: ^2.4.27 => 2.4.27
    gatsby-plugin-offline: ^3.2.26 => 3.2.26
    gatsby-plugin-react-helmet: ^3.3.10 => 3.3.10
    gatsby-plugin-sharp: ^2.6.31 => 2.6.31
    gatsby-plugin-styled-components: ^3.3.10 => 3.3.10
    gatsby-source-fetch: ^1.0.3 => 1.0.3
    gatsby-source-filesystem: ^2.3.27 => 2.3.27
    gatsby-source-graphql-universal: 3.3.0 => 3.3.0
    gatsby-source-prismic-graphql: ^3.6.2 => 3.6.2
    gatsby-transformer-csv: ^2.3.10 => 2.3.10
    gatsby-transformer-sharp: ^2.5.14 => 2.5.14
  npmGlobalPackages:
    gatsby-cli: 2.12.88

About this issue

Original URL
State: closed
Created 4 years ago
Reactions: 9
Comments: 26 (7 by maintainers)

Commits related to this issue

build: upgrade JS dependencies Locking Gatsby to older version. See https://github.com/gatsbyjs/gatsby/issues/26736 — committed to gsong/personal-site by gsong 4 years ago

Most upvoted comments

Same issue here. Downgrading it to "gatsby": "2.24.51" fixes it temporarily

Unfortunately this isn’t working for me. Current versions:

    // package.json
    "@prismicio/gatsby-source-prismic-graphql": "^3.6.13",
    ...
    "gatsby": "^2.24.51",

It builds up to here and then hangs…

j-mcgregor on Sep 15, 2020

Having this issue as well. This might be related to gatsby-source-prismic-graphql messing with the babel file to get their preview working.

PierreAndreis on Sep 11, 2020

I also get this error. Tried each suggestion with no luck. Currently investigating.

ttstauss on Sep 9, 2020

I since locked the Gatsby version to "gatsby": "2.24.51" in my package.json and re-installed. That appears to have resolved the issue, so it must be something with version "gatsby": "2.24.53" (I didn’t test the version between these two).

michaelpumo on Sep 1, 2020

Helps for me change gatsby version in package.json

"gatsby": "^2.24.53" => "gatsby": "2.24.51"

jan-vaclavik on Oct 16, 2020

I’m going to close this issue as there is nothing more to do from our side. I’ve created an issue https://github.com/prismicio/gatsby-source-graphql-universal/issues/13 so please move the discussion over there.

Thank you for using Gatsby 💪

wardpeet on Sep 16, 2020

I faced the same issue today.

RomSribn on Sep 10, 2020

Same issue here.

Walkeezy on Sep 10, 2020

I’m having the same issue. Just created this new project. I’m using "gatsby-source-prismic-graphql" just like the two above.

System:
    OS: macOS 10.15.6
    CPU: (8) x64 Intel(R) Core(TM) i5-8279U CPU @ 2.40GHz
    Shell: 3.2.57 - /bin/bash
  Binaries:
    Node: 12.18.2 - /usr/local/bin/node
    Yarn: 1.22.5 - /usr/local/bin/yarn
    npm: 6.14.8 - /usr/local/bin/npm
  Languages:
    Python: 2.7.16 - /usr/bin/python
  Browsers:
    Chrome: 85.0.4183.83
    Firefox: 72.0.2
    Safari: 13.1.2
  npmPackages:
    gatsby: ^2.24.49 => 2.24.53
    gatsby-image: ^2.4.16 => 2.4.16
    gatsby-plugin-manifest: ^2.4.27 => 2.4.27
    gatsby-plugin-preact: ^4.0.10 => 4.0.10
    gatsby-plugin-react-helmet: ^3.3.10 => 3.3.10
    gatsby-plugin-sharp: ^2.6.31 => 2.6.31
    gatsby-plugin-sitemap: ^2.4.12 => 2.4.12
    gatsby-plugin-webfonts: ^1.1.3 => 1.1.3
    gatsby-source-filesystem: ^2.3.27 => 2.3.27
    gatsby-source-prismic-graphql: ^3.6.2 => 3.6.2
    gatsby-transformer-sharp: ^2.5.14 => 2.5.14
  npmGlobalPackages:
    gatsby: 2.24.53

danniing on Sep 3, 2020