-
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
Missing class properties transform #31853
Comments
Thanks for the issue! We're also seeing this on the default blog starter and are investigating it (cc @vladar). Our current theory is that a recent |
For now one workaround to try: remove |
Facing the same issue and can confirm that the workaround proposed by @vladar works perfect:
|
The fix is published in |
I'm having the same issue with gatsby 3.10.1 inside a pnpm monorepo. When I go into
|
Just wanted to point out that it seems this issue wasn't entirely fixed in I am currently using version But yeah, looks like this issue may have come back up :/ |
@vladar running
Edit: The workaround #31853 (comment) does work though. |
Reporting same as above when updating from |
Got rid of the error via |
I am still having this error.. even when upgrading to v4... nothing works, tried removeing node_modules and lock files aswel as reinstallign everything. (i do not use yarn) |
the solution was adding a .babelrc with {
"plugins": [
["@babel/plugin-proposal-decorators", { "legacy": true }]
],
"presets": [
[
"babel-preset-gatsby",
{
"targets": {
"browsers": [">0.25%", "not dead"]
}
}
]
]
}
|
Executed `yarn-deduplicate && yarn` as it was suggested in gatsbyjs/gatsby#31853 (comment) to fix a gatsby/webpack error described in gatsbyjs/gatsby#31853
Executed `yarn-deduplicate && yarn` as it was suggested in gatsbyjs/gatsby#31853 (comment) to fix a gatsby/webpack error described in gatsbyjs/gatsby#31853
I've got no idea why removing the lock file works but hey, it really works! |
I got this
|
Did you try the workaround? |
I will and let you know, Thanks. |
I did the workaround but I didn't found any canges in git ?! |
thanks works for me |
rm -rf yarn.lock node_modules && yarn works for me, thanks! |
I had to remove node_modules in addition to the package-lock.json:
Thanks! |
Description
The build command crashes after updating to v3.7:
Steps to reproduce
I updated from
"gatsby": "^3.6.2"
=>"gatsby": "^3.7.0"
and ran into this issue. Not sure what is causing it yet.I see that there's been some updates to configs in this release, and I do export a config:
The crash does however persist if I remove this config.
Expected result
Gatsby should build without issues.
Actual result
The build crashes with what looks like a babel issue? Not 100% sure what's causing it yet.
Environment
No flags in my
gatsby-config
The text was updated successfully, but these errors were encountered: