Michal Piechowiak

`gatsby-remark-relative-images` (at least part that "rewrite" frontmatter paths) is not compatible with `gatsby@4`. In particular https://www.gatsbyjs.com/docs/reference/release-notes/migrating-from-v3-to-v4/#dont-mutate-nodes-outside-of-expected-apis is not handled

When I enabled debug mode made exactly to detect those problems I mentioned in previous comment (mode described in https://www.gatsbyjs.com/docs/how-to/local-development/debugging-missing-data/) I get: ``` success createSchemaCustomization - 0.014s warn Node mutation...

Hmm, this seems like the current code that make use `file-type` is just broken even with current version of that package - it now uses version 15 and it uses...

(disclaimer I'm one of the gatsby maintainers) > `console.error` is the same as `process.stderr.write` expect for the added newline. This is true, implementation wise in Node.js. I think it's worth...

Published new alpha version - `[email protected]`

Hi @lechinoix Your reproduction link ( https://github.com/Barooders/barooders-frontend ) 404s for me - is the url correct? Or maybe repository is private? I did try creating my own reproduction using `[email protected]`...

Does this actually work? From reading this it would try to `require()` a typescript file which wouldn't work in default Node.js environment unless some kind of "transpile TS on the...

Opened PR with changes that would follow nested presets in https://github.com/gatsbyjs/gatsby/pull/36249

Minor NIT is we probably shouldn't use `dontX` in internal field names - it made some sense in our initial conversation when we considered graphql directive (`@dontX` similar to `@dontInfer`),...

> Does Image CDN will only works on Gatsby Cloud? Not like normal hosting platforms. It does work now on Netlify properly using Netlify Image CDN (without extra hacks) and...