-
Notifications
You must be signed in to change notification settings - Fork 19
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
Babel loader broken. #3
Comments
@NathHorrigan could you supply a reproduction? This shouldn’t be an issue with new projects — but it’s possible something has been broken that your project was relying upon (e.g. a custom babel config file). Thanks! |
I could throw together a reproduction but are you sure there are no effects? because for example one of the functions called in the
However, My apologies if I'm missing something here. |
@NathHorrigan where are you seeing that line? Here’s the actual invocation, where you can see stage is passed. |
I'm also having a similar issue. I've created a project reproducing the issue I'm seeing here. I agree with @NathHorrigan that something introduced in Gatsby core over the past couple of days has impacted this plugin. When using Gatsby version 2.13.27, everything works great. Upon doing a reinstallation this afternoon of an existing project (and subsequently upgrading Gatsby to version 2.13.32), I began seeing issues in this project's
I'm using the gatsby-source-prismic-graphql plugin (version 3.3.1) to pull in content from Prismic, which in turn references gatsby-source-graphql-universal version v3.1.4 as a dependency. While using Gatsby version 2.13.32, when I run
Similarly,
Again, when I downgrade to Gatsby version 2.13.27, both |
I will take a look at this. We are monkey patching gatsby's graphql system so this is to be expected every now and then with major and minor releases but shouldn't be a problem with patches. Will keep you posted |
Currently breaks for me as well... |
Should be fixed with 3.1.6 |
The most recent changes from this PR (gatsbyjs/gatsby#15875) seem to have broken the babel-loader and it is not throwing the following errors:
The text was updated successfully, but these errors were encountered: