tailwindcss/tests/util
Robin Malfait dba5043591
Ensure all built-in plugins have tests (#11618)
* move `preflight` tests to `plugins` test folder

* move `container` tests to `plugins` test folder

* add a test that ensures that all built-in plugins have tests

This is based on a few assumptions:

1. All plugins exist in the `corePlugins.js` file and are exported as
   `corePlugins`
2. Each exported plugin in that object has a file with a corresponding
   name in the current (`tests/plugins/`) folder

* add dedicated plugin tests in the `plugins` folder

* add a test that ensures that all built-in variant plugins have tests

This is based on a few assumptions:

1. All variant plugins exist in the `corePlugins.js` file and are
   exported as `variantPlugins`
2. Each exported plugin in that object has a file with a corresponding
   name in the current (`tests/plugins/variants/`) folder

* add dedicated variant plugin tests in the `plugins/variants` folder

* cleanup basic usage test

* move existing animation tests to animation plugin tests

* move `apply-important-selector` tests to more appropriate location
2023-07-24 11:41:52 +02:00
..
defaults.js Explicitly configure Lightning CSS features, and prefer user browserslist over default browserslist (#11402) 2023-06-09 20:37:36 +02:00
run.js Ensure all built-in plugins have tests (#11618) 2023-07-24 11:41:52 +02:00
source-maps.js Fix source maps issue resulting in a crash (#11319) 2023-05-31 18:28:11 +02:00
strings.js Change how we handle defaults (optimized or not) (#6926) 2022-01-07 11:39:45 -05:00