feat: upgrading to gatsby 4 [DONT MERGE]

[jpvajda]

• Attempting to upgrade the OSS site to Gatsby 4.
• This PR also bumps the theme on the OSS site.
• this pr takes the approach about polyfills mentioned in this comment.
• this pr adds createNodeField

[gatsby-cloud[bot]]

Gatsby Cloud Build Report

opensource-website-develop

:tada: Your build was successful! See the Deploy preview here.

Build Details

View the build logs here.

:clock1: Build time: 4m

Performance

Lighthouse report

Metric	Score
Performance	:large_orange_diamond: 34
Accessibility	:large_orange_diamond: 88
Best Practices	:green_heart: 93
SEO	:large_orange_diamond: 85

:link: View full report

[jpvajda]

This passes all checks now.

[aswanson-nr]

Something is up with this build, it's missing most of the projects on the preview build. Running a build locally to see what I can find

[aswanson-nr]

No resolution yet, this is what I'm seeing:

• develop branch
  • dev and prod builds show data correctly
• gatsby4-upgrade branch
  • dev builds and shows all projects
  • prod build does not show any projects except for the layouts

[aswanson-nr]

Okay, I know why but I haven't fixed it yet. We are doing this and need to swap over to using createNodeField

[jpvajda]

FWIW: when building locally I see this error, which I believe is related to the use of the gatsby-newrelic-plugin

[@] winston-to-newrelic-logs: Error sending log data - Error: Request failed with status code 403

[jpvajda]

@rudouglas may have some context into the error I am seeing with the build plugin

https://github.com/newrelic-experimental/gatsby-build-newrelic/issues/30

[jpvajda]

This PR is helpful for the suggestion @aswanson-nr made https://github.com/gatsbyjs/gatsby/pull/33715

[jpvajda]

I made a change to use the createNodeField but the projects still aren't loading.. 🤔

[jpvajda]

I tried a different approach with the use of createNodeField what is interesting is locally I can load all the projects but when viewing the site on the preview build the projects do not load.

[stale[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be automatically closed if no further activity occurs. Thank you for your contributions.

[CLAassistant]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.

---

John P Vajda seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.
_{You have signed the CLA already but the status is still pending? Let us recheck it.}

[stale[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be automatically closed if no further activity occurs. Thank you for your contributions.

[stale[bot]]

This issue has been automatically closed because it was a stale issue that had no recent activity. Thank you for your contributions.