Gatsby 5 Umbrella Discussion #36609
Replies: 17 comments 29 replies
-
|
Getting what looks like peer-deps issues when running the |
Beta Was this translation helpful? Give feedback.
-
|
can you try installing with |
Beta Was this translation helpful? Give feedback.
-
|
If I |
Beta Was this translation helpful? Give feedback.
-
|
Seems like we are hitting npm/cli#4958 here. I am testing now wether we can force npm to use prerelease versions as candidates for peerDeps |
Beta Was this translation helpful? Give feedback.
-
|
gatsbyjs/gatsby-partial-hydration-starter#1 should fix the latter problem (when installed with I don't think we can really fix the regular |
Beta Was this translation helpful? Give feedback.
-
|
Somehow, for me
Caused by https://github.com/donavon/use-event-listener/blob/develop/src/index.js |
Beta Was this translation helpful? Give feedback.
-
|
Only change that comes to my mind we did and maybe is relevant: |
Beta Was this translation helpful? Give feedback.
-
|
Can you check if this also happens on |
Beta Was this translation helpful? Give feedback.
-
|
Hmm, that error occured without partial hydration. I'll check with latest v4, gimme some time 🙈 |
Beta Was this translation helpful? Give feedback.
-
|
@LekoArts so on v4, this error appears as soon I go from v4.23.1 to v4.24 So it might be related to partial hydration. It happens also when the flag is disabled. |
Beta Was this translation helpful? Give feedback.
-
|
The Slices API 🍕 has been added to the alpha! |
Beta Was this translation helpful? Give feedback.
-
|
Hey all! We're excited to announce we're now in Beta. 🔥 You can upgrade to the Gatsby 5 Beta by installing Thank you all for testing so far, and we are looking forward to hearing more about the beta. |
Beta Was this translation helpful? Give feedback.
-
|
Are there any plans to support ESM ? |
Beta Was this translation helpful? Give feedback.
-
|
Full ESM support is more important to me than anything else in v5. |
Beta Was this translation helpful? Give feedback.
-
|
Not as part of the initial 5.0 release, but the plan is to support ESM in Gatsby 5.x |
Beta Was this translation helpful? Give feedback.
-
|
Please see #31599 (comment) |
Beta Was this translation helpful? Give feedback.
-
|
A new version of GraphiQL will be available in Gatsby 5! You can use it now by installing
|
Beta Was this translation helpful? Give feedback.
-
|
Is there any work on updating the graphql source toolkit to graphql 16? This is needed for some other graphql source plugins. |
Beta Was this translation helpful? Give feedback.
-
|
GraphQL Toolkit is not currently being supported. We have plans in the future (Q1 2023) to continue improving the source plugin authoring experience. This might be a revised GraphQL Toolkit or possibly a new set of tools to help plugin authors. @smthomas is the product owner of that |
Beta Was this translation helpful? Give feedback.
-
|
I've got a fork of this that is working - https://github.com/nrandell/gatsby-graphql-toolkit and will be submitting a PR soon for that. |
Beta Was this translation helpful? Give feedback.
-
|
Is support for GraphQL fragments in |
Beta Was this translation helpful? Give feedback.
-
|
It's not something we implemented and it's also not high on our priority list. It shouldn't be blocked on anything, so if you (or someone else) wants to see this land in a v5.x, feel free to go ahead. |
Beta Was this translation helpful? Give feedback.
-
|
Hello, After trying to update my project to Gatsby 5 I'm running into an issue with It seems related to the latest update to GraphQL 16. My project is open source so feel free to pull to reproduce the error. Reproduction Linkhttps://github.com/r-ichard/gatsby-starter-bootstrap-5/tree/feature/gatsby-5 Steps to Reproduce
EnvironmentSystem:
OS: Linux 5.15 elementary OS 6.1 Jólnir
CPU: (8) x64 Intel(R) Core(TM) i7-8565U CPU @ 1.80GHz
Shell: 5.8 - /usr/bin/zsh
Binaries:
Node: 18.3.0 - ~/.nvm/versions/node/v18.3.0/bin/node
Yarn: 1.22.11 - /usr/local/bin/yarn
npm: 8.11.0 - ~/.nvm/versions/node/v18.3.0/bin/npm
Browsers:
Chrome: 106.0.5249.61
Firefox: 104.0
npmPackages:
gatsby: ^5.0.0-next.0 => 5.0.0-next.12
gatsby-plugin-gatsby-cloud: ^4.24.1-next.2 => 4.24.1
gatsby-plugin-image: ^2.24.0 => 2.24.0
gatsby-plugin-manifest: ^4.24.0 => 4.24.0
gatsby-plugin-offline: ^5.24.0 => 5.24.0
gatsby-plugin-sass: ^5.24.0 => 5.24.0
gatsby-plugin-sharp: ^4.24.0 => 4.24.0
gatsby-source-filesystem: ^4.24.0 => 4.24.0
gatsby-transformer-sharp: ^4.24.0 => 4.24.0Did you experience something similar ? |
Beta Was this translation helpful? Give feedback.
-
|
You also need to update all your other |
Beta Was this translation helpful? Give feedback.
-
|
Thanks a lot ! I didn't understand fully what the documentation meant. Here is how my package.json dependencies looks now : |
Beta Was this translation helpful? Give feedback.
-
|
@r-ichard I've added an example to that section, hope that helps |
Beta Was this translation helpful? Give feedback.
-
|
Hi! Current package.json dependencies: |
Beta Was this translation helpful? Give feedback.
-
|
I met the same (or similar) problem after updating Gatby from v4 to v5 (and related packages). Environment: ❯ node -v
v18.12.1
❯ npm -v
8.19.3with In my case, multiple versions (v16 and v15) of graphql are installed after I just updated Gatsby to v5: I have no idea how this is related but I did the following actions:
After that, only graphql of v16 is installed and the problem has gone. I hope this helps :) |
Beta Was this translation helpful? Give feedback.
-
|
The following issues might help people down the road: |
Beta Was this translation helpful? Give feedback.
-
|
Thanks a lot this solved the issue, it was a gatsby-theme so I've had to juggle all the dependencies a bit but it worked at the end! :) |
Beta Was this translation helpful? Give feedback.
-
|
I've updated from 4.24.1, and I still see that Head API is not wrapped in Providers. My app uses react-intl, and we have useIntl hook, which requires Provider to be in the tree, but wrapRootElement is not wrapping Head. There has been a promise to fix that in v5, but here we are, and my app is still broken. Way to go Gatsby team! @marvinjude #35841 (reply in thread) I'm seriously considering to use nextjs instead. At least they are backward compatible, if your is build only on hooks. |
Beta Was this translation helpful? Give feedback.
-
|
Don't know what you want to achieve with blackmailing us about moving to Next.js 🤷 If your use case is not yet working with Gatsby Head API, then use So please stop being so condescending and understand that running a project with X amount of users with X * 2 wishes for features will always push project maintainers into a situation where they have to prioritize things. Plus, it's all open source, you can send in a PR. |
Beta Was this translation helpful? Give feedback.
-
|
Yeah I was gonna say the same, I also have a very complex setup with |
Beta Was this translation helpful? Give feedback.
-
|
My issue is that I already has had converted the website to Head api from react-helmet, and it was the reason why I found an issue with missing context providers at first place, and keeping the PR open, waiting for wrapRootElement to be implemented. |
Beta Was this translation helpful? Give feedback.
-
|
Hi @JustFly1984, your whole attitude is not helping here; I would ask you to please be respectful and have a productive conversation rather than telling us what we should do and what we should not. As we mentioned before this didn't make the cut for 5.0 and will be shipped on 5.x. Meanwhile, feel free to create a detailed issue with the limitations you are hitting, PR are also very welcome if you are interested |
Beta Was this translation helpful? Give feedback.
-
|
Hello, I am using Gatbsy Cloud. When migrating from v4 to v5 my PR passed the Gatsby Build Service checks (all the feedback and advice above helped me get to that point 😄 ) ; however, after I merged my PR, I encountered the following error:
I have not seen this error before (and I cannot find other mentions of
In case it helps, my current and also: |
Beta Was this translation helpful? Give feedback.
-
|
This a silly suggestion, but can you try deleting the package-lock and node modules and fo a fresh install? |
Beta Was this translation helpful? Give feedback.
-
|
You should remove these from your package.json, too "@parcel/core": "^2.8.0",
"@parcel/runtime-browser-hmr": "^2.8.0",
"@parcel/runtime-service-worker": "^2.8.0",
"gatsby-parcel-config": "^1.2.0",
"graphql": "^16.6.0",
"sharp": "^0.31.2" |
Beta Was this translation helpful? Give feedback.
-
|
Thanks so much for the advice - I will try these and report back :) |
Beta Was this translation helpful? Give feedback.
-
|
I did both of the above, and everything is looking good now :) I am relatively new to Gatsby, so I appreciate the help - you probably saved me hours of fiddling. |
Beta Was this translation helpful? Give feedback.
-
|
Got
The error seems to be thrown from this line in loader.loadPage(...) may return something that's not a Promise when page is containing errors, according to loader.js gatsby/packages/gatsby/cache-dir/loader.js Lines 349 to 354 in dc3d741 FYI I'm still trying to figure out why the ChunkLoadError occurs, it looks like rendering a specific component from a third-party library is causing the error. |
Beta Was this translation helpful? Give feedback.
-
|
I am upgrading from Gatsby v4 to v5. Not sure if it's because I'm using windows and nvm, I am getting the following error when running
Update |
Beta Was this translation helpful? Give feedback.
-
|
We are in the process of upgrading from Gatsby 4.25.2 to 5.4.0, but we are seeing an issue with our plugins not loading. We currently have a monorepo setup like this We currently have several plugins that do not load on Gatsby v5 if they are using Another Note: If you have a I have been trying to figure out why these are not loading and the difference from v4.25.2 and v5, but I am unable to track down this specific change with as many changes that have happened. My question, is this a bug in v5+, or is this a bug in v3+/v4+ that got fixed in v5+. I didn't see anything related to this in the breaking changes section on the release notes that related to this type of import. I have also created a simple minimal repo here to show the issue. https://github.com/that1matt/gatsby-node-typescript-loading-error Changing the name of |
Beta Was this translation helpful? Give feedback.
-
|
I have tracked this down some more, and when calling the resolveJSFilepath it errors out, but doesn't throw an error as the resolveJSFilepath returns an empty string. Obviously the issue stems from only importing Still not sure if this is a bug, or something that was intentionally changed. Any help would be much appreciated. |
Beta Was this translation helpful? Give feedback.
-
Welcome to the overarching discussion related to the release of Gatsby 5! This discussion serves as the hub of all things related to the features, deprecations, breaking changes, docs, and testing that will be part of the general availability of Gatsby 5.
🚢 We plan on releasing Gatsby 5 in Q4 2022.
How you can help
Testing and providing feedback are the most valuable things you can do at this stage. Also, be sure to follow this discussion so that you know when we ship new canaries of Gatsby 5. Specific feedback we’re looking for:
gatsby-5Discord channelHow to get started with Gatsby 5
Creating a Project
Using our Starter
Clone the existing starter gatsby-starter-slices
cd gatsby-starter-slices npm install --legacy-peer-deps gatsby developUsing an online IDE
Using an existing project
Follow the Gatsby 4 to 5 migration guide.
Using Partial Hydration (experimental)
Please visit RFC: Partial Hydration to learn more.
So, what’s shipping with Gatsby 5?
We’re shipping two major improvements to Gatsby in Gatsby 5:
A handful of breaking changes will happen, please see the Gatsby 4 to 5 migration guide. The update process will be smooth.
Where can I ask questions?
gatsby-5Discord channelBeta Was this translation helpful? Give feedback.
All reactions