-
Notifications
You must be signed in to change notification settings - Fork 156
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
Migrate to Gatsby v5 #43
Open
alcrene
wants to merge
9
commits into
wkocjan:master
Choose a base branch
from
alcrene:wkocjan
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Noteworthy changes: - Custom types (WorkHistoryYaml and ProjectsYaml) are now created with `createSchemaCustomization` instead of `createTypes`. + 'sourceNodes.js' is now (with a few modifications) 'createSchema.js' - Replace use of Helm by the new Head API + 'lang' is now set in gatsby-ssr.js - To support setting 'lang' in gatsby-ssr, a new plugin argument 'lang' is added. + This replaces the previous 'siteMetadata: local' argument - TailwindCSS is upgraded to v3 + dark mode option set to "media" + 'content' and 'safelist' options updated to v3 format
Remove duplicated dependencies: gatsby, react, react-dom were listed under both "dependencies" and "peerDependencies" -> Removed from "dependencies" Add @babel/core Remove index.js
Support for dark mode essentially just means adding `dark:*` variants to all color utility classes. Changing `showThemeLogo` to be passed by `context` (https://www.gatsbyjs.com/docs/creating-and-modifying-pages) avoids the need to retrieve that flag via a GraphQL query. It also makes sense to set this option at build time. GraphQL queries can't really be shadowed (see gatsbyjs/gatsby#36920) so passing flags in this way makes it easier for users to modify the theme without having to fork the whole thing.
- Now works with with yarn v2+ (in this case 3.5.0) - Update all dependencies to their most recent version. - Bump theme version to 3.0.0 - !! Changed package name from `gatsby-theme-intro` to `@wkocjan/gatsby-theme-intro` !! + This corresponds to its scoped name on npm & the gatsby plugin repo + Since `site` has the dependency `"@wkocjan/gatsby-theme-intro": "*"`, using a matching name allows yarn correctly use the version from the workspace rather than pulling the one from the online repo.
Remove debug output on console Re-add "main": "index.js" in package.json
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This migrates the theme to the latest version of Gatsby (v5).
Other noteworthy changes:
showThemeLogo
is no longer accessed via GraphQL query, making it easier for theme shadowing.