mirror of
https://github.com/tailwindlabs/tailwindcss.git
synced 2025-12-08 21:36:08 +00:00
a4f1ff9052
* drop empty lines when diffing output * replace expected css with optimized lightningcss output Lightning CSS generates a more optimal CSS output. Right now the tests are setup in a way that both the generated css and expected css are run through `lightningcss` to make sure that the output is concistent for the `stable` and `oxide` engines. But this also means that the expected output _could_ be larger (aka not optimized) and still matches (after it runs through lightningcss). By replacing this with the more optimal output we achieve a few things: 1. This better reflects reality since we will be using `lightningcss`. 2. This gets rid of unnecessary css. 3. Removed code!
23 lines
761 B
JavaScript
23 lines
761 B
JavaScript
import { crosscheck, run, html, css, defaults } from './util/run'
|
|
|
|
crosscheck(({ stable, oxide }) => {
|
|
stable.test.todo('space-x uses physical properties')
|
|
oxide.test('space-x uses logical properties', () => {
|
|
let config = {
|
|
content: [{ raw: html`<div class="space-x-4"></div>` }],
|
|
corePlugins: { preflight: false },
|
|
}
|
|
|
|
return run('@tailwind base; @tailwind utilities;', config).then((result) => {
|
|
expect(result.css).toMatchCss(css`
|
|
${defaults}
|
|
.space-x-4 > :not([hidden]) ~ :not([hidden]) {
|
|
--tw-space-x-reverse: 0;
|
|
margin-inline-start: calc(1rem * calc(1 - var(--tw-space-x-reverse)));
|
|
margin-inline-end: calc(1rem * var(--tw-space-x-reverse));
|
|
}
|
|
`)
|
|
})
|
|
})
|
|
})
|