-
Notifications
You must be signed in to change notification settings - Fork 10.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Generating SSR bundle failed saying it's not possible to compile spread arguments in super()
without compiling classes
#29326
Comments
I am seeing the same issue. The error is originated from this change in Force resolving |
same here |
Hi! Sorry to hear you're running into an issue. To help us best begin debugging the underlying cause, it is incredibly helpful if you're able to create a minimal reproduction. This is a simplified example of the issue that makes it clear and obvious what the issue is and how we can begin to debug it. If you're up for it, we'd very much appreciate if you could provide a minimal reproduction and we'll be able to take another look. Thanks for using Gatsby! 💜 |
There's no reproduction needed, all our sites used to build but no longer do. As @Pessimistress mentioned, The one-line fix is: But Gatsby itself badly needs to lock the version otherwise you're going to get a whole lot of people opening issues. |
We got the same error. This is blocking our production environment. |
We got the same error. This is blocking our production environment. Error: https://github.com/antvis/G2Plot/runs/1827390584?check_suite_focus=true |
Are you using default constructor for yours react component? Overriding constructor should help: |
Just use react function component |
I also have the same problem here. However, it is with the I tried to add I believe that in this case the plugin cannot move the |
@guilhermebellotti
|
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
{
"presets": [ "babel-preset-gatsby" ]
} |
@LekoArts Here is the minimal repro that I can manage:
import React from "react"
export default class Home extends React.Component {
state = {};
render() {
return <div>Hello world!</div>;
}
}
The issue, as I understand it, is that
|
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
Add
Let's test! After correcting this 'bug', I will need to |
…hange gatsbyjs/gatsby#29326 Signed-off-by: Paul Bastide <pbastide@us.ibm.com>
@guilhermebellotti You do not need to add the dependency as it's already required by
|
@Pessimistress
I am not using classes in this project, only functional components. But probably dependencies do. |
I tried to roll back to previous version of all dependencies. But the issue remains:
|
After rolling back all the gatsby updates and adding:
Thanks @Pessimistress I am going to try not to touch any gatsby dependencies for the next weeks now. |
Thanks to @Pessimistress for steps to reproduce - minimal reproduction available at https://github.com/pieh/i29326 |
i have solved in my project:
|
For more information on the build error see gatsbyjs/gatsby#29326
I've got the same issue and this solved it. Thanks @visiky |
We published |
I can confirm that it works in my case. @pieh thanks so much and please have an enjoyable weekend |
When running `npm run start` the build would fail when creating the development build files. gatsbyjs/gatsby#29326
This appears to be fixed in the latest Gatsby version as noted here: gatsbyjs/gatsby#29326 (comment)
… Quill use document.
Description
gatsby build is failing with the error:-
Here's the screenshot of the build logs:-
Steps to reproduce
Clone https://github.com/pieh/i29326 and use steps from README of that repo
Expected result
Build should be successful
Actual result
Build failed
Environment
Run
gatsby info --clipboard
in your project directory and paste the output here.System:
OS: Windows 10 10.0.18363
CPU: (8) x64 Intel(R) Core(TM) i5-8250U CPU @ 1.60GHz
Binaries:
Node: 14.15.1 - C:\Program Files\nodejs\node.EXE
Yarn: 1.22.4 - C:\Program Files (x86)\Yarn\bin\yarn.CMD
npm: 6.14.8 - C:\Program Files\nodejs\npm.CMD
Languages:
Python: 2.7.15
Browsers:
Chrome: 88.0.4324.146
Edge: Spartan (44.18362.449.0)
npmPackages:
gatsby: 2.32.0 => 2.32.0
gatsby-image: 2.11.0 => 2.11.0
gatsby-link: 2.11.0 => 2.11.0
gatsby-plugin-canonical-urls: 2.10.0 => 2.10.0
gatsby-plugin-google-gtag: 2.8.0 => 2.8.0
gatsby-plugin-layout: 1.10.0 => 1.10.0
gatsby-plugin-lunr: 1.5.2 => 1.5.2
gatsby-plugin-manifest: 2.12.0 => 2.12.0
gatsby-plugin-no-sourcemaps: 2.9.0 => 2.9.0
gatsby-plugin-preconnect: ^1.1.54 => 1.1.54
gatsby-plugin-react-helmet: 3.10.0 => 3.10.0
gatsby-plugin-remove-serviceworker: 1.0.0 => 1.0.0
gatsby-plugin-robots-txt: 1.5.5 => 1.5.5
gatsby-plugin-sharp: 2.14.0 => 2.14.0
gatsby-plugin-sitemap: 2.12.0 => 2.12.0
gatsby-source-filesystem: 2.11.0 => 2.11.0
gatsby-source-shopify: 3.10.0 => 3.10.0
gatsby-transformer-sharp: 2.12.0 => 2.12.0
npmGlobalPackages:
gatsby-cli: 2.12.91
The text was updated successfully, but these errors were encountered: