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

breaking(gatsby-plugin-postcss): Upgrade gatsby-plugin-postcss to PostCSS 8 #26947

Merged
merged 9 commits into from
Oct 1, 2020
Merged

breaking(gatsby-plugin-postcss): Upgrade gatsby-plugin-postcss to PostCSS 8 #26947

merged 9 commits into from
Oct 1, 2020

Conversation

christophervoigt
Copy link
Contributor

Description

Updating postcss-loader and adding postcss to dependencies for gatsby-plugin-postcss.

Related Issues

Fixes #26939

This commit is supposed to solve #26939
@gatsbot gatsbot bot added the status: triage needed Issue or pull request that need to be triaged and assigned to a reviewer label Sep 18, 2020
@LekoArts LekoArts added type: feature or enhancement Issue that is not a bug and requests the addition of a new feature or enhancement. and removed status: triage needed Issue or pull request that need to be triaged and assigned to a reviewer labels Sep 21, 2020
@LekoArts LekoArts added status: blocked This issue/PR can't be solved at the moment and shouldn't be closed/merged and removed status: blocked This issue/PR can't be solved at the moment and shouldn't be closed/merged labels Sep 22, 2020
@christophervoigt
Copy link
Contributor Author

@LekoArts what are the next steps on this PR? Seems like it just needs a review?

@moonmeister
Copy link
Contributor

@chlorophyllkid Thanks for working on this. I believe we would want postcss as a peerDependency. https://evilmartians.com/chronicles/postcss-8-plugin-migration/#step-1-move-postcss-to-peerdependencies

@christophervoigt
Copy link
Contributor Author

Wouldn't that mean the install instructions of the plugin itself would need a change too?
Because a user then has to install postcss separately?

@moonmeister
Copy link
Contributor

Correct. But either way this will be a breaking change. This way we'll be letting people choose the postcss version that's compatible with their plugins.

@LekoArts
Copy link
Contributor

Yeah, we'll be releasing a new major version then so the breaking change is okay 👍

@christophervoigt
Copy link
Contributor Author

Alright, in that case I'll update the PR later. 👍🏼

@wardpeet wardpeet changed the title Upgrade gatsby-plugin-postcss to PostCSS 8 breaking(gatsby-plugin-postcss): Upgrade gatsby-plugin-postcss to PostCSS 8 Sep 25, 2020
Copy link
Contributor

@LekoArts LekoArts left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for the PR! 👍

@LekoArts LekoArts merged commit 00f7c08 into gatsbyjs:master Oct 1, 2020
@LekoArts
Copy link
Contributor

LekoArts commented Oct 1, 2020

Successfully published:
 - [email protected]

pragmaticpat pushed a commit to pragmaticpat/gatsby that referenced this pull request Apr 28, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type: feature or enhancement Issue that is not a bug and requests the addition of a new feature or enhancement.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Upgrade gatsby-plugin-postcss to PostCSS 8
4 participants