Grayson Hicks

@oorestisime I am open to maintaining if you want to discuss transferring Github and NPM ownership!

Hi @ovflowd ! I gave this a run locally and believe the MDX v2 syntax in the `content/blog/releases` folder is causing the issue. I ran the posts through an MDX...

No problem @ovflowd . I only tested on the `test/gatsby-crash` branch. How are the MD files in `releases` being generated? That's likely where a change needs to happen, maybe something...

@ovflowd Thanks for pointing to that larger discussion, I think I found and fixed a lot of the errors you had already seen 😅 . Interestingly, you note in that...

Confirmed several of the issues I found were syntax errors introduced in MDXv2, so I'm not sure why those would be failing on MDXv1: https://mdxjs.com/docs/troubleshooting-mdx/#unexpected-end-of-file-in-expression-expected-a-corresponding-closing-brace-for-

So I was still unable to find a local linting solution that showed the same errors I was able to find by running through the MDX compiler. *But*, I reintroduced...

The `test/gatsby-crashes` branch builds for me successfully with that change (or with the syntax changes).

I don't know, I'm just letting you know what can unblock you.

[The Gatsby check uses webpack global defined here](https://github.com/gatsbyjs/gatsby/blob/master/packages/gatsby/src/utils/webpack.config.js#L233). Not sure why preact is making that falsy?

FWIW, I don't think Preact is really close to compat with React 18 at this point: https://github.com/preactjs/preact/issues/2621#issuecomment-1129562148