-
-
Notifications
You must be signed in to change notification settings - Fork 546
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
feat: Update theme-ui to v0.3.x #371
Merged
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
|
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.
Theme UI updated to v0.3 a while ago and I now finally had time to go through the breaking changes: https://theme-ui.com/migrating#v03
In general this update should be painless and without any breaking changes (for most people). The sites look and function identical, it was more a technical refactoring.
Breaking Changes
These changes might be breaking for some people:
@lekoarts/gatsby-theme-specimens
: Renamed thetheme
prop on the<Heading />
component toconfig
@lekoarts/gatsby-theme-specimens
&@lekoarts/gatsby-theme-styleguide
: Removedtheme-ui
as a direct dependency and moved them topeerDependencies
. This supersedes the PR fix(deps): make theme-ui a peerDependency #262Description
gatsby
,react
,react-dom
packages to latest version@emotion/core
and@mdx-js/react
packages astheme-ui
now comes with it<Styled.root />
components as Theme UI now places that on thebody
by defaultStyled.x
with e.g.Link
,Heading
@emotion/core
,@mdx-js/mdx
&@mdx-js/react
toyarn resolutions
to only have one version of each dependencymerge
fromtheme-ui
for config merging<Global />
by moving stuff to the Theme UI config