-
Notifications
You must be signed in to change notification settings - Fork 10.3k
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
chore(themes): move themes into starters and packages #16178
chore(themes): move themes into starters and packages #16178
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good. Configs have been reset to the previous values so 👍. Not sure if any testing needs to be done.
@wardpeet Shouldn’t need any testing per se but let’s wait on a go ahead from the themes team? Cc @johno @ChristopherBiscardi @gatsbyjs/themes-core |
So turns out adding starters to the workspace breaks in all sorts of ridiculous ways 😂 https://app.circleci.com/jobs/github/gatsbyjs/gatsby/182460 fails with https://app.circleci.com/jobs/github/gatsbyjs/gatsby/182462 fails because of some snapshot mismatches where it expects Another snapshot test fails (it transforms HTML img tags). This one is strange. |
7dfd4c9
to
e9256bd
Compare
e9256bd
to
36386fe
Compare
Right now, until gatsbyjs#16178 starters aren't managed by lerna so their dependencies haven't been updated. There have been a handful of bugfixes that aren't being installed by default until the user upgrades their dependencies.
Closing this in favour of a new one because holy hell look at those conflicts |
leaving a post-close comment that this approach is good with me and we'll work out whatever we need to with |
Why
Theme packages should now be publishable (is that even a word) by lerna
What
This pull request