* make `jit` mode the default when no mode is specified
* unify JIT and AOT codepaths
* ensure `Object.entries` on undefined doesn't break
It could be that sometimes you don't have values in your config (e.g.: `presets: []`), this in turn will break some plugins where we assume we have a value.
* drop AOT specific tests
These tests are all covered by JIT mode already and were AOT specific.
* simplify tests, and add a few
Some of the tests were written for AOT specifically, some were missing. We also updated the way we write those tests, essentially making Tailwind a blackbox, by testing against the final output.
Now that JIT mode is the default, this is super fast because we only generate what is used, instead of partially testing in a 3MB file or building it all, then purging.
* add some todo's to make sure we warn in a few cases
* make `darkMode: 'media'`, the default
This also includes moving dark mode tests to its own dedicated file.
* remove PostCSS 7 compat mode
* update CLI to be JIT-first
* fix integration tests
This is not a _real_ fix, but it does solve the broken test for now.
* warn when using @responsive or @variants
* remove the JIT preview warning
* remove AOT-only code paths
* remove all `mode: 'jit'` blocks
Also remove `variants: {}` since they are not useful in `JIT` mode
anymore.
* drop unused dependencies
* rename `purge` to `content`
* remove static CDN builds
* mark `--purge` as deprecated in the CLI
This will still work, but a warning will be printed and it won't show up
in the `--help` output.
* cleanup nesting plugin
We don't have to duplicate it anymore since there is no PostCSS 7
version anymore.
* make sure integration tests run in band
* cleanup folder structure
* make sure nesting folder is available
* simplify resolving of purge/content information
* change specific selector to universal selector
This is the commit that we could "undo" in the future if we need it
again.
* simplify `relative-purge-paths` test
This test doesn't require the "reset" selector (whether it is super specific or universal)
Simplified it so that it tests the relative purge config and nothing else.
* added css tagged template literal helpers
This allows prettier to format the string as CSS. This improves formatting and will improve future diffs.
* drop tailwind headers in the sanity tests
Every time we bump the Tailwind version, the sanity tests fail, because
the current version is encoded in the fixture files.
This will ensure that all of the contents is still checked and the
header is skipped. The header will be tested against a regex to ensure
that it is still there.
This should be a small but nice QoL improvement, so that we don't have
to think about updating those tests whenever we fix bugs or land new
features.
* WIP
* run prettier
* drop new lines in custom matcher
Drop all newlines, let prettier handle everything for us.
* add cache for the selector parser
* add `@apply` tests for the universal optimizer
* drop comments
* initial replacements
* WIP
* WIP
* MAKE IT WORK
* Rename to resolveDefaultsAtRules
* Update tests + defaults identifiers
* Don't add @defaults in AOT mode
Co-authored-by: Robin Malfait <malfait.robin@gmail.com>
