-
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
fix(gatsby-transformer-remark): ensure getNodesByType()
is passed through
#28218
fix(gatsby-transformer-remark): ensure getNodesByType()
is passed through
#28218
Conversation
Not sure why the CI failed - possibly a Yarn PnP related issue? |
The PnP patch for typescript is out of date, we've updated it but haven't released it yet. Will be fixed in the next release of Yarn |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ah, thanks for the fix @hassankhan
I will not block this PR on PnP tests because this one doesn't change any dependencies or imports so it won't impact PnP. @merceyz is there some way to subscribe / get notification when new version is released? We do have pinned yarn/berry version in our test setup - Line 322 in b346804
We might want to revisit this setup because #28238 happened at some point that possible could have been prevented with different setup |
If you remove these lines your tests will always run against the latest stable releases (because of this). For notifications we don't currently have a good way of being aware of them (apart following us on Twitter 😄), but I'll look into that for 3.x, as part of the release automation work I plan to do. |
…hrough (#28218) (#28261) (cherry picked from commit 7867897) Co-authored-by: Hassan Khan <[email protected]>
Description
Add
getNodesByType()
to the other parameters so it is correctly passed through to Gatsby Remark plugins.Documentation
https://www.gatsbyjs.com/tutorial/remark-plugin-tutorial/
Related Issues