Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

PostCSS 8

See original GitHub issue

Is your proposal related to a problem?

PostCSS 8 was released. It added a new plugin API. Right now Gatsby does not support PostCSS 8 plugins.

Describe the solution you’d like

Updating postcss-loader and adding postcss to dependencies will fix the problem.

Describe alternatives you’ve considered

N/A

Additional context

PostCSS 8 changelog does not have breaking changes related to CRA 4 only removing Node.js 6 and 8 support).

Issue Analytics

State:
Created 3 years ago
Reactions:124
Comments:29 (3 by maintainers)

Top GitHub Comments

99reactions

mrmckebcommented, Jun 18, 2021

Hi all, we’re hoping to get this out as a part of 4.1. @raix has already done the hard work, so we just needed to bump to a new version of 8.x.

Please see #11121 for the exact version. 4.1 is coming very soon, but I can’t give an exact date sorry.

86reactions

zackdotcomputercommented, Feb 28, 2021

For anyone else who comes here and wonders what’s up with this issue, I’ll save you some clicks and summarize the state of the related PRs:

PR #9716 above was closed in favor of #10003, which was merged.
That PR was then reverted by #10216 because dependencies postcss-normalize and postcss-browser-comments were both still using postcss@7
PostCSS-Normalize is separately tracking their need to update here
Not much has happened in January or February on this issue.