gatsby: Generating SSR bundle failed saying it's not possible to compile spread arguments in `super()` without compiling classes

@guilhermebellotti @babel/plugin-transform-spread is a dependency of babel-preset-gatsby. Just adding it to your own package.json does not mean that 7.12.1 is used. You can see this with npm list/yarn ls.

npm dedup may fix it, or if you are using yarn, add a resolutions field to package.json.

Really! I didn’t know this selection of yarn dependencies. Thanks for the help and clarification!

In the end, I solved it this way:

Run commands

1. gatsby clean
2. rm -rf yarn.lock
3. rm -rf node_modules/
4. yarn add @babel/plugin-transform-spread@7.12.1

Add resolutions in package.json file

  "resolutions": {
    "@babel/plugin-transform-spread": "7.12.1"
  },

Let’s test! yarn install gatsby build

After correcting this ‘bug’, I will need to remove the resolutions and the dependency "@babel/plugin-transform-spread": "7.12.1", correct @Pessimistress?

There’s no reproduction needed, all our sites used to build but no longer do.

As @Pessimistress mentioned, @babel/plugin-transform-spread pushed a patch that broke many things, I think Gatsby just needs to lock the version.

The one-line fix is: npm i @babel/plugin-transform-spread@7.12.1

But Gatsby itself badly needs to lock the version otherwise you’re going to get a whole lot of people opening issues.

We published gatsby@2.32.3 which should contain fix ( https://github.com/gatsbyjs/gatsby/pull/29346 )

I am seeing the same issue. The error is originated from this change in @babel/plugin-transform-spread: https://github.com/babel/babel/pull/12722

Force resolving @babel/plugin-transform-spread to 7.12.1 fixes it.

@guilhermebellotti @babel/plugin-transform-spread is a dependency of babel-preset-gatsby. Just adding it to your own package.json does not mean that 7.12.1 is used. You can see this with npm list/yarn ls.

npm dedup may fix it, or if you are using yarn, add a resolutions field to package.json.

I was able to workaround this build issue on Netlify by installing the suggested version of @babel/plugin-transform-spread@7.12.1 and also added a custom babel config with babel-preset-gatsby.

1. npm i @babel/plugin-transform-spread@7.12.1

2. npm i babel-preset-gatsby

3. Add a .babelrc to the root of the project with the following json:

{  
  "presets": [ "babel-preset-gatsby" ]
}

@guilhermebellotti @babel/plugin-transform-spread is a dependency of babel-preset-gatsby. Just adding it to your own package.json does not mean that 7.12.1 is used. You can see this with npm list/yarn ls. npm dedup may fix it, or if you are using yarn, add a resolutions field to package.json.

Really! I didn’t know this selection of yarn dependencies. Thanks for the help and clarification!

In the end, I solved it this way:

Run commands

1. gatsby clean
2. rm -rf yarn.lock
3. rm -rf node_modules/
4. yarn add @babel/plugin-transform-spread@7.12.1

Add resolutions in package.json file

  "resolutions": {
    "@babel/plugin-transform-spread": "7.12.1"
  },

Let’s test! yarn install gatsby build

After correcting this ‘bug’, I will need to remove the resolutions and the dependency "@babel/plugin-transform-spread": "7.12.1", correct @Pessimistress?

i have solved in my project:

npm uninstall @babel/plugin-transform-spread        
npm install @babel/plugin-transform-spread@7.12.1

@guilhermebellotti You do not need to add the dependency as it’s already required by babel-preset-gatsby. Removing the resolution may still cause problems later because if @babel/preset-env@7.12.13 is installed, it will ask for @babel/plugin-transform-spread@^7.12.13. The following steps work for my projects:

• rm yarn.lock
• Add the following to package.json:

"resolutions": {
  "@babel/preset-env": "7.12.11",
  "@babel/plugin-transform-spread": "7.12.1"
},

• yarn
• Remove the “resolutions” field from package.json