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.
We want to use
PostCSS 8
in Tailwind, however a lot of tools are not compatible withPostCSS 7
yet. To account for this we can will create a separate tag on npm:To get the repo into
PostCSS 7
mode we have to runyarn compat
ornpm run compat
. This will prepare the repo for PostCSS 7 mode. Essentially it will do multiple things:yarn babelify
, to ensure that we have the latest and greatest buildpackage.json
to include dependencies from thepackage.postcss7.json
file, it will deeply merge all the valueslib/index.postcss7.js
as entry point, this will allow us to use the "old" PostCSS Plugin register system.Once you run this command, you will get the following output:
2 important parts here are the publish with the
--tag
ofcompat
, this allows for thenpm install tailwindcss@compat
.To restore everything to normal, you can use the
yarn compat:restore
ornpm run compat:restore
. This does the inverse and uses the oldpackage.json
andlib/index.js
entry point.This will output: