gatsby Brand new install with 5.14 produces many errors, develop terminates with errors

Brand new install with 5.14 produces many errors, develop terminates with errors

Open kylegoetz opened this issue 9 months ago • 2 comments

Preliminary Checks

[x] This issue is not a duplicate. Before opening a new issue, please search existing issues: https://github.com/gatsbyjs/gatsby/issues
[x] This issue is not a question, feature request, RFC, or anything other than a bug report directly related to Gatsby. Please post those things in GitHub Discussions: https://github.com/gatsbyjs/gatsby/discussions

Description

Can't even run develop on a brand new project immediately after gatsby new

Reproduction Link

https://github.com/gatsbyjs/gatsby

Steps to Reproduce

Fresh install of Gatsby 5.14
gatsby new (right away we get ERROR: UNKNOWN and then a punycode deprecation warning
Gatsby continues despite the error, so select TypeScript, no CMS, Tailwind CSS, responsive images
installation from there gives no errors, great!
cd into path and gatsby develop

errors galore

and terminates with not finished source and transform nodes - 0.058s

Expected Result

I expect that gatsby develop doesn't error out immediately after gatsby new && cd ...

Actual Result

See screenshots.

Environment

System:
    OS: macOS 15.0.1
    CPU: (8) arm64 Apple M1 Pro
    Shell: 5.9 - /bin/zsh
  Binaries:
    Node: 23.1.0 - /opt/homebrew/bin/node
    Yarn: 1.22.17 - /opt/homebrew/bin/yarn
    npm: 10.9.0 - /opt/homebrew/bin/npm
  Browsers:
    Chrome: 133.0.6943.141
    Safari: 18.0.1
  npmPackages:
    gatsby: ^5.14.1 => 5.14.1
    gatsby-plugin-image: ^3.14.0 => 3.14.0
    gatsby-plugin-postcss: ^6.14.0 => 6.14.0
    gatsby-plugin-sharp: ^5.14.0 => 5.14.0
    gatsby-source-filesystem: ^5.14.0 => 5.14.0
    gatsby-transformer-sharp: ^5.14.0 => 5.14.0
  npmGlobalPackages:
    gatsby-cli: 5.14.0