2023-01-20 12:45:04 -05:00
|
|
|
import { crosscheck, run, html, css } from './util/run'
|
Remove AOT (#5340)
* 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
2021-09-01 17:13:59 +02:00
|
|
|
|
2023-01-20 12:45:04 -05:00
|
|
|
crosscheck(({}) => {
|
|
|
|
|
test('options are not required', () => {
|
|
|
|
|
let config = { content: [{ raw: html`<div class="container"></div>` }] }
|
2018-03-13 13:50:44 -04:00
|
|
|
|
2023-01-20 12:45:04 -05:00
|
|
|
return run('@tailwind components', config).then((result) => {
|
|
|
|
|
expect(result.css).toMatchFormattedCss(css`
|
Remove AOT (#5340)
* 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
2021-09-01 17:13:59 +02:00
|
|
|
.container {
|
2023-01-20 12:45:04 -05:00
|
|
|
width: 100%;
|
2020-07-15 10:44:17 -04:00
|
|
|
}
|
2023-01-20 12:45:04 -05:00
|
|
|
@media (min-width: 640px) {
|
|
|
|
|
.container {
|
|
|
|
|
max-width: 640px;
|
|
|
|
|
}
|
2020-07-15 10:44:17 -04:00
|
|
|
}
|
2023-01-20 12:45:04 -05:00
|
|
|
@media (min-width: 768px) {
|
|
|
|
|
.container {
|
|
|
|
|
max-width: 768px;
|
|
|
|
|
}
|
Remove AOT (#5340)
* 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
2021-09-01 17:13:59 +02:00
|
|
|
}
|
2023-01-20 12:45:04 -05:00
|
|
|
@media (min-width: 1024px) {
|
|
|
|
|
.container {
|
|
|
|
|
max-width: 1024px;
|
|
|
|
|
}
|
2020-07-15 10:44:17 -04:00
|
|
|
}
|
2023-01-20 12:45:04 -05:00
|
|
|
@media (min-width: 1280px) {
|
|
|
|
|
.container {
|
|
|
|
|
max-width: 1280px;
|
|
|
|
|
}
|
2020-07-15 10:44:17 -04:00
|
|
|
}
|
2023-01-20 12:45:04 -05:00
|
|
|
@media (min-width: 1536px) {
|
|
|
|
|
.container {
|
|
|
|
|
max-width: 1536px;
|
|
|
|
|
}
|
2020-07-15 10:44:17 -04:00
|
|
|
}
|
2023-01-20 12:45:04 -05:00
|
|
|
`)
|
|
|
|
|
})
|
Remove AOT (#5340)
* 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
2021-09-01 17:13:59 +02:00
|
|
|
})
|
2019-03-14 14:54:20 -04:00
|
|
|
|
2023-01-20 12:45:04 -05:00
|
|
|
test('screens can be passed explicitly', () => {
|
|
|
|
|
let config = {
|
|
|
|
|
content: [{ raw: html`<div class="container"></div>` }],
|
|
|
|
|
theme: {
|
|
|
|
|
container: {
|
|
|
|
|
screens: ['400px', '500px'],
|
|
|
|
|
},
|
2019-05-12 18:50:03 -04:00
|
|
|
},
|
2023-01-20 12:45:04 -05:00
|
|
|
}
|
2019-05-12 18:50:03 -04:00
|
|
|
|
2023-01-20 12:45:04 -05:00
|
|
|
return run('@tailwind components', config).then((result) => {
|
|
|
|
|
expect(result.css).toMatchFormattedCss(css`
|
Remove AOT (#5340)
* 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
2021-09-01 17:13:59 +02:00
|
|
|
.container {
|
2023-01-20 12:45:04 -05:00
|
|
|
width: 100%;
|
2020-07-15 10:44:17 -04:00
|
|
|
}
|
2023-01-20 12:45:04 -05:00
|
|
|
@media (min-width: 400px) {
|
|
|
|
|
.container {
|
|
|
|
|
max-width: 400px;
|
|
|
|
|
}
|
2020-07-15 10:44:17 -04:00
|
|
|
}
|
2023-01-20 12:45:04 -05:00
|
|
|
@media (min-width: 500px) {
|
|
|
|
|
.container {
|
|
|
|
|
max-width: 500px;
|
|
|
|
|
}
|
|
|
|
|
}
|
|
|
|
|
`)
|
|
|
|
|
})
|
Remove AOT (#5340)
* 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
2021-09-01 17:13:59 +02:00
|
|
|
})
|
2019-05-12 18:50:03 -04:00
|
|
|
|
2023-01-20 12:45:04 -05:00
|
|
|
test('screens are ordered ascending by min-width', () => {
|
|
|
|
|
let config = {
|
|
|
|
|
content: [{ raw: html`<div class="container"></div>` }],
|
|
|
|
|
theme: {
|
|
|
|
|
container: {
|
|
|
|
|
screens: ['500px', '400px'],
|
2019-05-12 18:50:03 -04:00
|
|
|
},
|
|
|
|
|
},
|
2023-01-20 12:45:04 -05:00
|
|
|
}
|
2019-05-12 18:50:03 -04:00
|
|
|
|
2023-01-20 12:45:04 -05:00
|
|
|
return run('@tailwind components', config).then((result) => {
|
|
|
|
|
expect(result.css).toMatchFormattedCss(css`
|
Remove AOT (#5340)
* 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
2021-09-01 17:13:59 +02:00
|
|
|
.container {
|
2023-01-20 12:45:04 -05:00
|
|
|
width: 100%;
|
2020-07-15 10:44:17 -04:00
|
|
|
}
|
2023-01-20 12:45:04 -05:00
|
|
|
@media (min-width: 400px) {
|
|
|
|
|
.container {
|
|
|
|
|
max-width: 400px;
|
|
|
|
|
}
|
2020-07-15 10:44:17 -04:00
|
|
|
}
|
2023-01-20 12:45:04 -05:00
|
|
|
@media (min-width: 500px) {
|
|
|
|
|
.container {
|
|
|
|
|
max-width: 500px;
|
|
|
|
|
}
|
|
|
|
|
}
|
|
|
|
|
`)
|
|
|
|
|
})
|
Remove AOT (#5340)
* 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
2021-09-01 17:13:59 +02:00
|
|
|
})
|
2019-05-12 18:50:03 -04:00
|
|
|
|
2023-01-20 12:45:04 -05:00
|
|
|
test('screens are deduplicated by min-width', () => {
|
|
|
|
|
let config = {
|
|
|
|
|
content: [{ raw: html`<div class="container"></div>` }],
|
|
|
|
|
theme: {
|
|
|
|
|
container: {
|
|
|
|
|
screens: {
|
|
|
|
|
sm: '576px',
|
|
|
|
|
md: '768px',
|
|
|
|
|
'sm-only': { min: '576px', max: '767px' },
|
|
|
|
|
},
|
|
|
|
|
},
|
2019-03-13 21:04:45 -04:00
|
|
|
},
|
2023-01-20 12:45:04 -05:00
|
|
|
}
|
Remove AOT (#5340)
* 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
2021-09-01 17:13:59 +02:00
|
|
|
|
2023-01-20 12:45:04 -05:00
|
|
|
return run('@tailwind components', config).then((result) => {
|
|
|
|
|
expect(result.css).toMatchFormattedCss(css`
|
Remove AOT (#5340)
* 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
2021-09-01 17:13:59 +02:00
|
|
|
.container {
|
2023-01-20 12:45:04 -05:00
|
|
|
width: 100%;
|
2020-07-15 10:44:17 -04:00
|
|
|
}
|
2023-01-20 12:45:04 -05:00
|
|
|
@media (min-width: 576px) {
|
|
|
|
|
.container {
|
|
|
|
|
max-width: 576px;
|
|
|
|
|
}
|
2020-07-15 10:44:17 -04:00
|
|
|
}
|
2023-01-20 12:45:04 -05:00
|
|
|
@media (min-width: 768px) {
|
|
|
|
|
.container {
|
|
|
|
|
max-width: 768px;
|
|
|
|
|
}
|
2020-07-15 10:44:17 -04:00
|
|
|
}
|
2023-01-20 12:45:04 -05:00
|
|
|
`)
|
|
|
|
|
})
|
Remove AOT (#5340)
* 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
2021-09-01 17:13:59 +02:00
|
|
|
})
|
2018-03-13 13:50:44 -04:00
|
|
|
|
2023-01-20 12:45:04 -05:00
|
|
|
test('the container can be centered by default', () => {
|
|
|
|
|
let config = {
|
|
|
|
|
content: [{ raw: html`<div class="container"></div>` }],
|
|
|
|
|
theme: {
|
|
|
|
|
container: {
|
|
|
|
|
center: true,
|
|
|
|
|
},
|
2019-03-13 21:04:45 -04:00
|
|
|
},
|
2023-01-20 12:45:04 -05:00
|
|
|
}
|
Remove AOT (#5340)
* 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
2021-09-01 17:13:59 +02:00
|
|
|
|
2023-01-20 12:45:04 -05:00
|
|
|
return run('@tailwind components', config).then((result) => {
|
|
|
|
|
expect(result.css).toMatchFormattedCss(css`
|
2020-07-15 10:44:17 -04:00
|
|
|
.container {
|
2023-01-20 12:45:04 -05:00
|
|
|
width: 100%;
|
|
|
|
|
margin-left: auto;
|
2023-01-31 15:37:49 +01:00
|
|
|
margin-right: auto;
|
2020-07-15 10:44:17 -04:00
|
|
|
}
|
2023-01-20 12:45:04 -05:00
|
|
|
@media (min-width: 640px) {
|
|
|
|
|
.container {
|
|
|
|
|
max-width: 640px;
|
|
|
|
|
}
|
2020-07-15 10:44:17 -04:00
|
|
|
}
|
2023-01-20 12:45:04 -05:00
|
|
|
@media (min-width: 768px) {
|
|
|
|
|
.container {
|
|
|
|
|
max-width: 768px;
|
|
|
|
|
}
|
2020-07-15 10:44:17 -04:00
|
|
|
}
|
2023-01-20 12:45:04 -05:00
|
|
|
@media (min-width: 1024px) {
|
|
|
|
|
.container {
|
|
|
|
|
max-width: 1024px;
|
|
|
|
|
}
|
2020-07-15 10:44:17 -04:00
|
|
|
}
|
2023-01-20 12:45:04 -05:00
|
|
|
@media (min-width: 1280px) {
|
|
|
|
|
.container {
|
|
|
|
|
max-width: 1280px;
|
|
|
|
|
}
|
|
|
|
|
}
|
|
|
|
|
@media (min-width: 1536px) {
|
|
|
|
|
.container {
|
|
|
|
|
max-width: 1536px;
|
|
|
|
|
}
|
2020-07-15 10:44:17 -04:00
|
|
|
}
|
2023-01-20 12:45:04 -05:00
|
|
|
`)
|
|
|
|
|
})
|
Remove AOT (#5340)
* 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
2021-09-01 17:13:59 +02:00
|
|
|
})
|
2018-03-13 13:50:44 -04:00
|
|
|
|
2023-01-20 12:45:04 -05:00
|
|
|
test('horizontal padding can be included by default', () => {
|
|
|
|
|
let config = {
|
|
|
|
|
content: [{ raw: html`<div class="container"></div>` }],
|
|
|
|
|
theme: {
|
|
|
|
|
container: {
|
|
|
|
|
padding: '2rem',
|
2020-02-26 11:43:23 +00:00
|
|
|
},
|
|
|
|
|
},
|
2023-01-20 12:45:04 -05:00
|
|
|
}
|
2020-02-26 11:43:23 +00:00
|
|
|
|
2023-01-20 12:45:04 -05:00
|
|
|
return run('@tailwind components', config).then((result) => {
|
|
|
|
|
expect(result.css).toMatchFormattedCss(css`
|
2020-07-15 10:44:17 -04:00
|
|
|
.container {
|
2023-01-20 12:45:04 -05:00
|
|
|
width: 100%;
|
Remove AOT (#5340)
* 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
2021-09-01 17:13:59 +02:00
|
|
|
padding-left: 2rem;
|
2023-01-31 15:37:49 +01:00
|
|
|
padding-right: 2rem;
|
2020-07-15 10:44:17 -04:00
|
|
|
}
|
2023-01-20 12:45:04 -05:00
|
|
|
@media (min-width: 640px) {
|
|
|
|
|
.container {
|
|
|
|
|
max-width: 640px;
|
|
|
|
|
}
|
2020-07-15 10:44:17 -04:00
|
|
|
}
|
2023-01-20 12:45:04 -05:00
|
|
|
@media (min-width: 768px) {
|
|
|
|
|
.container {
|
|
|
|
|
max-width: 768px;
|
|
|
|
|
}
|
2020-07-15 10:44:17 -04:00
|
|
|
}
|
2023-01-20 12:45:04 -05:00
|
|
|
@media (min-width: 1024px) {
|
|
|
|
|
.container {
|
|
|
|
|
max-width: 1024px;
|
|
|
|
|
}
|
|
|
|
|
}
|
|
|
|
|
@media (min-width: 1280px) {
|
|
|
|
|
.container {
|
|
|
|
|
max-width: 1280px;
|
|
|
|
|
}
|
2020-07-15 10:44:17 -04:00
|
|
|
}
|
2023-01-20 12:45:04 -05:00
|
|
|
@media (min-width: 1536px) {
|
|
|
|
|
.container {
|
|
|
|
|
max-width: 1536px;
|
|
|
|
|
}
|
|
|
|
|
}
|
|
|
|
|
`)
|
|
|
|
|
})
|
Remove AOT (#5340)
* 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
2021-09-01 17:13:59 +02:00
|
|
|
})
|
2020-02-26 11:43:23 +00:00
|
|
|
|
2023-01-20 12:45:04 -05:00
|
|
|
test('responsive horizontal padding can be included by default', () => {
|
|
|
|
|
let config = {
|
|
|
|
|
content: [{ raw: html`<div class="container"></div>` }],
|
|
|
|
|
theme: {
|
|
|
|
|
screens: {
|
|
|
|
|
sm: '576px',
|
|
|
|
|
md: { min: '768px' },
|
|
|
|
|
lg: { 'min-width': '992px' },
|
|
|
|
|
xl: { min: '1200px', max: '1600px' },
|
|
|
|
|
},
|
|
|
|
|
container: {
|
|
|
|
|
padding: {
|
|
|
|
|
DEFAULT: '1rem',
|
|
|
|
|
sm: '2rem',
|
|
|
|
|
lg: '4rem',
|
|
|
|
|
xl: '5rem',
|
|
|
|
|
},
|
|
|
|
|
},
|
2019-03-13 21:04:45 -04:00
|
|
|
},
|
2023-01-20 12:45:04 -05:00
|
|
|
}
|
2018-03-13 13:50:44 -04:00
|
|
|
|
2023-01-20 12:45:04 -05:00
|
|
|
return run('@tailwind components', config).then((result) => {
|
|
|
|
|
expect(result.css).toMatchFormattedCss(css`
|
2020-07-15 10:44:17 -04:00
|
|
|
.container {
|
2023-01-20 12:45:04 -05:00
|
|
|
width: 100%;
|
|
|
|
|
padding-left: 1rem;
|
2023-01-31 15:37:49 +01:00
|
|
|
padding-right: 1rem;
|
2020-07-15 10:44:17 -04:00
|
|
|
}
|
2023-01-20 12:45:04 -05:00
|
|
|
@media (min-width: 576px) {
|
|
|
|
|
.container {
|
|
|
|
|
max-width: 576px;
|
|
|
|
|
padding-left: 2rem;
|
2023-01-31 15:37:49 +01:00
|
|
|
padding-right: 2rem;
|
2023-01-20 12:45:04 -05:00
|
|
|
}
|
|
|
|
|
}
|
|
|
|
|
@media (min-width: 768px) {
|
|
|
|
|
.container {
|
|
|
|
|
max-width: 768px;
|
|
|
|
|
}
|
|
|
|
|
}
|
|
|
|
|
@media (min-width: 992px) {
|
|
|
|
|
.container {
|
|
|
|
|
max-width: 992px;
|
|
|
|
|
padding-left: 4rem;
|
2023-01-31 15:37:49 +01:00
|
|
|
padding-right: 4rem;
|
2023-01-20 12:45:04 -05:00
|
|
|
}
|
|
|
|
|
}
|
|
|
|
|
@media (min-width: 1200px) {
|
|
|
|
|
.container {
|
|
|
|
|
max-width: 1200px;
|
|
|
|
|
padding-left: 5rem;
|
2023-01-31 15:37:49 +01:00
|
|
|
padding-right: 5rem;
|
2023-01-20 12:45:04 -05:00
|
|
|
}
|
2020-07-15 10:44:17 -04:00
|
|
|
}
|
2023-01-20 12:45:04 -05:00
|
|
|
`)
|
|
|
|
|
})
|
Remove AOT (#5340)
* 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
2021-09-01 17:13:59 +02:00
|
|
|
})
|
2020-07-15 14:13:27 -04:00
|
|
|
|
2023-01-20 12:45:04 -05:00
|
|
|
test('setting all options at once', () => {
|
|
|
|
|
let config = {
|
|
|
|
|
content: [{ raw: html`<div class="container"></div>` }],
|
|
|
|
|
theme: {
|
|
|
|
|
container: {
|
|
|
|
|
screens: ['400px', '500px'],
|
|
|
|
|
center: true,
|
|
|
|
|
padding: '2rem',
|
|
|
|
|
},
|
2020-07-15 14:13:27 -04:00
|
|
|
},
|
2023-01-20 12:45:04 -05:00
|
|
|
}
|
2020-07-15 14:13:27 -04:00
|
|
|
|
2023-01-20 12:45:04 -05:00
|
|
|
return run('@tailwind components', config).then((result) => {
|
|
|
|
|
expect(result.css).toMatchFormattedCss(css`
|
|
|
|
|
.container {
|
Remove AOT (#5340)
* 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
2021-09-01 17:13:59 +02:00
|
|
|
width: 100%;
|
2023-01-20 12:45:04 -05:00
|
|
|
margin-left: auto;
|
2023-01-31 15:37:49 +01:00
|
|
|
margin-right: auto;
|
2023-01-20 12:45:04 -05:00
|
|
|
padding-left: 2rem;
|
2023-01-31 15:37:49 +01:00
|
|
|
padding-right: 2rem;
|
2020-07-15 14:13:27 -04:00
|
|
|
}
|
|
|
|
|
@media (min-width: 400px) {
|
2023-01-20 12:45:04 -05:00
|
|
|
.container {
|
Remove AOT (#5340)
* 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
2021-09-01 17:13:59 +02:00
|
|
|
max-width: 400px;
|
2020-07-15 14:13:27 -04:00
|
|
|
}
|
|
|
|
|
}
|
|
|
|
|
@media (min-width: 500px) {
|
2023-01-20 12:45:04 -05:00
|
|
|
.container {
|
Remove AOT (#5340)
* 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
2021-09-01 17:13:59 +02:00
|
|
|
max-width: 500px;
|
2020-07-15 14:13:27 -04:00
|
|
|
}
|
|
|
|
|
}
|
2023-01-20 12:45:04 -05:00
|
|
|
`)
|
|
|
|
|
})
|
|
|
|
|
})
|
|
|
|
|
|
|
|
|
|
test('container can use variants', () => {
|
|
|
|
|
let config = {
|
|
|
|
|
content: [{ raw: html`<div class="lg:hover:container"></div>` }],
|
|
|
|
|
theme: {
|
|
|
|
|
container: {
|
|
|
|
|
screens: ['400px', '500px'],
|
|
|
|
|
},
|
|
|
|
|
},
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
return run('@tailwind components', config).then((result) => {
|
|
|
|
|
expect(result.css).toMatchFormattedCss(css`
|
|
|
|
|
@media (min-width: 1024px) {
|
|
|
|
|
.lg\:hover\:container:hover {
|
|
|
|
|
width: 100%;
|
|
|
|
|
}
|
|
|
|
|
@media (min-width: 400px) {
|
|
|
|
|
.lg\:hover\:container:hover {
|
|
|
|
|
max-width: 400px;
|
|
|
|
|
}
|
|
|
|
|
}
|
|
|
|
|
@media (min-width: 500px) {
|
|
|
|
|
.lg\:hover\:container:hover {
|
|
|
|
|
max-width: 500px;
|
|
|
|
|
}
|
|
|
|
|
}
|
|
|
|
|
}
|
|
|
|
|
`)
|
|
|
|
|
})
|
Remove AOT (#5340)
* 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
2021-09-01 17:13:59 +02:00
|
|
|
})
|
2020-07-15 14:13:27 -04:00
|
|
|
})
|