Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Updated: gatsby to 3.12.0 #37

Open
wants to merge 2 commits into
base: master
Choose a base branch
from

Conversation

DalSoft
Copy link

@DalSoft DalSoft commented Aug 23, 2021

Updated: gatsby to 3.12.0

  • Updated: gatsby to 3.12.0, tailwind to 2.2.7, react to 17.0.2 and typescript to 4.3.5
  • Updated gatsby-config.ts to include fast dev flags
  • Updated .gitignore to ignore __generated__ folder
  • Deleted __generated__ folder from repo

Darran added 2 commits August 23, 2021 11:15
…script: 4.3.5

Also updated gatsby-config.ts to include fast flags and updated .gitignore to remove__generated__ folder.
@ahmad-reza619
Copy link
Collaborator

Hello thank you for contributing

I see that you're upgrading some deps, and some of the upgrades are major upgrade, have you tested it on your local machine?

@DalSoft
Copy link
Author

DalSoft commented Aug 31, 2021

@ahmad-reza619 I'm using my fork now and it's working perfectly. However, there are some warnings (doesn't stop it building / working though) messages because of this change:

"resolutions": {
    "graphql": "^15.4.0",
    "graphql-compose": "^7.25.0",
    "webpack": "^5.24.2"
  }

The warnings are happening because some of the plugins haven't been upgraded to use the latest version of graphql yet. The above config says use 15.4.0, and the warnings are just letting us know that this what is happening.

I got this from the gatsby migration guide and it doesn't work without this in package.json.

Also, I'd like to say IMO this is one of the best Gatsby starters (and it now works on v3 of Gatsby 😊) because it already has everything you need tailwind, SEO, theming, etc without going overboard.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants