tailwindcss/tests/tailwind-screens.test.js
Robin Malfait a4f1ff9052
Improve CSS output in tests to better reflect reality (#10454)
* 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!
2023-01-31 15:37:49 +01:00

66 lines
1.4 KiB
JavaScript

import { crosscheck, run, html, css } from './util/run'
crosscheck(() => {
test('class variants are inserted at `@tailwind variants`', async () => {
let config = {
content: [{ raw: html`<div class="font-bold hover:font-bold md:font-bold"></div>` }],
}
let input = css`
@tailwind utilities;
@tailwind variants;
.foo {
color: black;
}
`
return run(input, config).then((result) => {
expect(result.css).toMatchFormattedCss(css`
.font-bold,
.hover\:font-bold:hover {
font-weight: 700;
}
@media (min-width: 768px) {
.md\:font-bold {
font-weight: 700;
}
}
.foo {
color: #000;
}
`)
})
})
test('`@tailwind screens` works as an alias for `@tailwind variants`', async () => {
let config = {
content: [{ raw: html`<div class="font-bold hover:font-bold md:font-bold"></div>` }],
}
let input = css`
@tailwind utilities;
@tailwind screens;
.foo {
color: black;
}
`
return run(input, config).then((result) => {
expect(result.css).toMatchFormattedCss(css`
.font-bold,
.hover\:font-bold:hover {
font-weight: 700;
}
@media (min-width: 768px) {
.md\:font-bold {
font-weight: 700;
}
}
.foo {
color: #000;
}
`)
})
})
})