You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Any Gatsby project errors with "cannot read property 'resolved' of undefined" #12851
Hey @KyleAMathews! We really appreciate you taking the time to report an issue. The collaborators on this project attempt to help as many people as possible, but we're a limited number of volunteers, so it's possible this won't be addressed swiftly.
If you need any help, or just have general Babel or JavaScript questions, we have a vibrant Slack community that typically always has someone willing to help. You can sign-up here for an invite."
Hi @KyleAMathews! This issue is missing some important information we'll need to be able to reproduce this issue.
Please understand that we receive a high volume of issues, and there are only a limited number of volunteers that help maintain this project. The easier it is for us to decipher an issue with the info provided, the more likely it is that we'll be able to help.
Please make sure you have the following information documented in this ticket:
Your Babel configuration (typically from .babelrc or babel.config.js)
Please provide either a link to the problem via the repl, or if the repl is insufficient, a new and minimal repository with instructions on how to build/replicate the issue.
I am seeing the same, with a minimal gatsby site (created by npm init gatsby -y).
The logs I'm getting from gatsby develop are:
ERROR #98123 WEBPACK
Generating development SSR bundle failed
Cannot read property 'resolved' of undefined
File: .cache/ssr-develop-static-entry.js
not finished Building development bundle - 0.301s
I was able to unblock myself by adding resolutions to my package.json as well:
(At least I'm seeing things locally, can't get the codesandbox server to start, but here's the repo in case it helps: https://github.com/gillkyle/babel-repro)
cc @nicolo-ribaudo (or whoever, thanks for looking into this 🙂)
Activity
babel-bot commentedon Feb 22, 2021
Hey @KyleAMathews! We really appreciate you taking the time to report an issue. The collaborators on this project attempt to help as many people as possible, but we're a limited number of volunteers, so it's possible this won't be addressed swiftly.
If you need any help, or just have general Babel or JavaScript questions, we have a vibrant Slack community that typically always has someone willing to help. You can sign-up here for an invite."
nicolo-ribaudo commentedon Feb 22, 2021
Can you share the complete stack trace or a reproduction repo?
babel-bot commentedon Feb 22, 2021
Hi @KyleAMathews! This issue is missing some important information we'll need to be able to reproduce this issue.
Please understand that we receive a high volume of issues, and there are only a limited number of volunteers that help maintain this project. The easier it is for us to decipher an issue with the info provided, the more likely it is that we'll be able to help.
Please make sure you have the following information documented in this ticket:
.babelrcorbabel.config.js)Please provide either a link to the problem via the
repl, or if thereplis insufficient, a new and minimal repository with instructions on how to build/replicate the issue.gillkyle commentedon Feb 22, 2021
I am seeing the same, with a minimal gatsby site (created by
npm init gatsby -y).The logs I'm getting from
gatsby developare:I was able to unblock myself by adding
resolutionsto my package.json as well:Will try to spin up a minimal reproduction now...
gillkyle commentedon Feb 22, 2021
Here's a minimal site with the latest packages installed where I'm seeing the error: https://codesandbox.io/s/github/gillkyle/babel-repro
(At least I'm seeing things locally, can't get the codesandbox server to start, but here's the repo in case it helps: https://github.com/gillkyle/babel-repro)
cc @nicolo-ribaudo (or whoever, thanks for looking into this 🙂)
KyleAMathews commentedon Feb 22, 2021
The error is happening in our config merging logic https://github.com/gatsbyjs/gatsby/blob/255b56575f69787884655a3642afbb3ea90f8869/packages/gatsby/src/utils/babel-loader-helpers.js#L117-L142
This bit of code https://github.com/gatsbyjs/gatsby/blob/255b56575f69787884655a3642afbb3ea90f8869/packages/gatsby/src/utils/babel-loader-helpers.js#L100-L105 used to generate an object but now it returns a generator (console.log outputs)
Object [Generator] {}nicolo-ribaudo commentedon Feb 22, 2021
Thanks, working on a fix.
KyleAMathews commentedon Feb 23, 2021
Another one #12854