Lennart

No problem! I've resurfaced this internally and will see that you get an answer :)

Hi! Since we didn't receive an answer for 7 days or more about the ask of a reproduction I'm going to close this now, as we can't do much to...

TODOs from other PR: - https://github.com/gatsbyjs/gatsby/pull/35751#issuecomment-1141859593 - https://github.com/gatsbyjs/gatsby/pull/35751#discussion_r885381904 - https://github.com/gatsbyjs/gatsby/pull/35751#discussion_r885662293

This update changes the `failOnError` option to `failOn` with a string literal. We probably should update our docs when we update to this version to not recommend using a deprecated...

I've handled the old and new option now Papertrail: - https://github.com/lovell/sharp/blob/main/docs/changelog.md#v0304---18th-april-2022 - https://sharp.pixelplumbing.com/api-constructor#parameters - https://github.com/lovell/sharp/commit/926572b41ea363ede57189128441a42fb77f66f4

Happy to review a PR changing this! https://www.gatsbyjs.com/contributing/how-to-open-a-pull-request/

Hey, thanks for the PR! We should expand the information given here instead: https://www.gatsbyjs.com/docs/how-to/custom-configuration/typescript/#pageprops We could extend it to something like this: ```tsx import * as React from "react" import...

Just to understand it correctly: So your use case would be that you define the PageProps and then some component will access the `location` of `PageProps` to use it for...

Feel free to take whatever item from that list. We appreciate any PR, no matter if small/easy or big/complicated file :)

It's hard to help from the outside without any reproduction. webpack isn't the fastest hot-reloading anymore compared to other solutions so depending on your setup it mights just be the...