2024-03-05 14:23:26 +01:00
|
|
|
{
|
|
|
|
|
"name": "@tailwindcss/root",
|
|
|
|
|
"private": true,
|
|
|
|
|
"version": "1.0.0",
|
|
|
|
|
"prettier": {
|
|
|
|
|
"semi": false,
|
|
|
|
|
"singleQuote": true,
|
|
|
|
|
"printWidth": 100,
|
|
|
|
|
"plugins": [
|
|
|
|
|
"prettier-plugin-organize-imports"
|
|
|
|
|
],
|
|
|
|
|
"overrides": [
|
|
|
|
|
{
|
|
|
|
|
"files": [
|
|
|
|
|
"tsconfig.json"
|
|
|
|
|
],
|
|
|
|
|
"options": {
|
|
|
|
|
"parser": "jsonc"
|
|
|
|
|
}
|
Add integration test setup and tests for the Vite integration (#14089)
This PR adds a new root `/integrations` folder that will be the home of
integration tests. The idea of these tests is to use Tailwind in various
setups just like our users would (by only using the publishable npm
builds).
To avoid issues with concurrent tests making changes to the file system,
to make it very easy to test through a range of versions, and to avoid
changing configuration objects over and over in test runs, we decided to
inline the scaffolding completely into the test file and have no
examples checked into the repo.
Here's an example of how this can look like for a simple Vite test:
```ts
test('works with production builds', {
fs: {
'package.json': json`
{
"type": "module",
"dependencies": {
"@tailwindcss/vite": "workspace:^",
"tailwindcss": "workspace:^"
},
"devDependencies": {
"vite": "^5.3.5"
}
}
`,
'vite.config.ts': ts`
import tailwindcss from '@tailwindcss/vite'
import { defineConfig } from 'vite'
export default defineConfig({
build: { cssMinify: false },
plugins: [tailwindcss()],
})
`,
'index.html': html`
<head>
<link rel="stylesheet" href="./src/index.css">
</head>
<body>
<div class="underline m-2">Hello, world!</div>
</body>
`,
'src/index.css': css`
@import 'tailwindcss/theme' reference;
@import 'tailwindcss/utilities';
`,
},
},
async ({ fs, exec }) => {
await exec('pnpm vite build')
expect.assertions(2)
for (let [path, content] of await fs.glob('dist/**/*.css')) {
expect(path).toMatch(/\.css$/)
expect(stripTailwindComment(content)).toMatchInlineSnapshot(
`
".m-2 {
margin: var(--spacing-2, .5rem);
}
.underline {
text-decoration-line: underline;
}"
`,
)
}
},
)
```
By defining all dependencies this way, we never have to worry about
which fixtures are checked in and can more easily describe changes to
the setup.
For ergonomics, we've also added the [`embed` prettier
plugin](https://github.com/Sec-ant/prettier-plugin-embed). This will
mean that files inlined in the `fs` setup are properly indented. No
extra work needed!
If you're using VS Code, I can also recommend the [Language
Literals](https://marketplace.visualstudio.com/items?itemName=sissel.language-literals)
extension so that syntax highlighting also _just works_.
A neat feature of inlining the scaffolding like this is to make it very
simple to test through a variety of versions. For example, here's how we
can set up a test against Vite 5 and Vite 4:
```js
;['^4.5.3', '^5.3.5'].forEach(viteVersion => {
test(`works with production builds for Vite ${viteVersion}`, {
fs: {
'package.json': json`
{
"type": "module",
"devDependencies": {
"vite": "${viteVersion}"
}
}
`,
async () => {
// Do something
},
)
})
```
## Philosophy
Before we dive into the specifics, I want to clearly state the design
considerations we have chosen for this new test suite:
- All file mutations should be done in temp folders, nothing should ever
mess with your working directory
- Windows as a first-class citizen
- Have a clean and simple API that describes the test setup only using
public APIs
- Focus on reliability (make sure cleanup scripts work and are tolerant
to various error scenarios)
- If a user reports an issue with a specific configuration, we want to
be able to reproduce them with integration tests, no matter how obscure
the setup (this means the test need to be in control of most of the
variables)
- Tests should be reasonably fast (obviously this depends on the
integration. If we use a slow build tool, we can't magically speed it
up, but our overhead should be minimal).
## How it works
The current implementation provides a custom `test` helper function
that, when used, sets up the environment according to the configuration.
It'll create a new temporary directory and create all files, ensuring
things like proper `\r\n` line endings on Windows.
We do have to patch the `package.json` specifically, since we can not
use public versions of the tailwindcss packages as we want to be able to
test against a development build. To make this happen, every `pnpm
build` run now creates tarballs of the npm modules (that contain only
the files that would also in the published build). We then patch the
`package.json` to rewrite `workspace:^` versions to link to those
tarballs. We found this to work reliably on Windows and macOS as well as
being fast enough to not cause any issues. Furthermore we also decided
to use `pnpm` as the version manager for integration tests because of
it's global module cache (so installing `vite` is fast as soon as you
installed it once).
The test function will receive a few utilities that it can use to more
easily interact with the temp dir. One example is a `fs.glob` function
that you can use to easily find files in eventual `dist/` directories or
helpers around `spawn` and `exec` that make sure that processes are
cleaned up correctly.
Because we use tarballs from our build dependencies, working on changes
requires a workflow where you run `pnpm build` before running `pnpm
test:integrations`. However it also means we can run clients like our
CLI client with no additional overhead—just install the dependency like
any user would and set up your test cases this way.
## Test plan
This PR also includes two Vite specific integration tests: One testing a
static build (`pnpm vite build`) and one a dev mode build (`pnpm vite
dev`) that also makes changes to the file system and asserts that the
resources properly update.
---------
Co-authored-by: Robin Malfait <malfait.robin@gmail.com>
2024-08-02 11:50:49 +02:00
|
|
|
},
|
|
|
|
|
{
|
|
|
|
|
"files": [
|
|
|
|
|
"integrations/**/*.ts"
|
|
|
|
|
],
|
|
|
|
|
"options": {
|
|
|
|
|
"plugins": [
|
|
|
|
|
"prettier-plugin-embed",
|
|
|
|
|
"prettier-plugin-organize-imports"
|
|
|
|
|
]
|
|
|
|
|
}
|
2024-03-05 14:23:26 +01:00
|
|
|
}
|
|
|
|
|
]
|
|
|
|
|
},
|
|
|
|
|
"scripts": {
|
|
|
|
|
"format": "prettier --write .",
|
|
|
|
|
"lint": "prettier --check . && turbo lint",
|
2024-08-09 19:57:16 +02:00
|
|
|
"build": "turbo build --filter=!./playgrounds/*",
|
|
|
|
|
"postbuild": "node ./scripts/pack-packages.mjs",
|
2024-03-05 14:23:26 +01:00
|
|
|
"dev": "turbo dev --filter=!./playgrounds/*",
|
2024-10-23 20:52:09 +02:00
|
|
|
"test": "cargo test && vitest run --hideSkippedTests",
|
2026-01-06 16:23:46 +01:00
|
|
|
"test:integrations": "vitest --root=./integrations",
|
2025-01-07 09:57:34 -05:00
|
|
|
"test:ui": "pnpm run --filter=tailwindcss test:ui && pnpm run --filter=@tailwindcss/browser test:ui",
|
2024-10-23 20:52:09 +02:00
|
|
|
"tdd": "vitest --hideSkippedTests",
|
2024-03-05 14:23:26 +01:00
|
|
|
"bench": "vitest bench",
|
|
|
|
|
"version-packages": "node ./scripts/version-packages.mjs",
|
|
|
|
|
"vite": "pnpm run --filter=vite-playground dev",
|
|
|
|
|
"nextjs": "pnpm run --filter=nextjs-playground dev"
|
|
|
|
|
},
|
|
|
|
|
"license": "MIT",
|
|
|
|
|
"devDependencies": {
|
Bump dependencies (#19608)
This PR bumps a bunch of dependencies. This also moves a few
dependencies that we use in multiple packages to the pnpm catalog.
Closes: #19603, #19604, #19576, #19575, #19573, #19565, #19547, #19546,
#19545, #19609, #19581, #19620, #19619
- #19603
- #19604
- #19576
- #19575
- #19573
- #19565
- #19547
- #19546
- #19545
- #19609
- #19581
- https://github.com/tailwindlabs/tailwindcss/pull/19620
- #19620
- #19619
## Test Plan
All tests in CI should still pass. [ci-all]
2026-02-04 12:38:50 +01:00
|
|
|
"@playwright/test": "^1.58.0",
|
2024-08-09 16:12:24 +02:00
|
|
|
"@types/node": "catalog:",
|
2025-06-26 11:28:01 +02:00
|
|
|
"postcss": "8.5.6",
|
2025-06-24 09:57:35 -04:00
|
|
|
"postcss-import": "^16.1.1",
|
2025-02-10 10:54:45 +01:00
|
|
|
"prettier": "catalog:",
|
2025-12-26 12:36:51 -05:00
|
|
|
"prettier-plugin-embed": "^0.5.1",
|
2025-09-26 16:10:41 -04:00
|
|
|
"prettier-plugin-organize-imports": "^4.3.0",
|
2025-11-19 18:18:45 -05:00
|
|
|
"tsup": "^8.5.1",
|
Bump dependencies (#19608)
This PR bumps a bunch of dependencies. This also moves a few
dependencies that we use in multiple packages to the pnpm catalog.
Closes: #19603, #19604, #19576, #19575, #19573, #19565, #19547, #19546,
#19545, #19609, #19581, #19620, #19619
- #19603
- #19604
- #19576
- #19575
- #19573
- #19565
- #19547
- #19546
- #19545
- #19609
- #19581
- https://github.com/tailwindlabs/tailwindcss/pull/19620
- #19620
- #19619
## Test Plan
All tests in CI should still pass. [ci-all]
2026-02-04 12:38:50 +01:00
|
|
|
"turbo": "^2.7.6",
|
2024-08-09 16:12:24 +02:00
|
|
|
"typescript": "^5.5.4",
|
Bump dependencies (#19608)
This PR bumps a bunch of dependencies. This also moves a few
dependencies that we use in multiple packages to the pnpm catalog.
Closes: #19603, #19604, #19576, #19575, #19573, #19565, #19547, #19546,
#19545, #19609, #19581, #19620, #19619
- #19603
- #19604
- #19576
- #19575
- #19573
- #19565
- #19547
- #19546
- #19545
- #19609
- #19581
- https://github.com/tailwindlabs/tailwindcss/pull/19620
- #19620
- #19619
## Test Plan
All tests in CI should still pass. [ci-all]
2026-02-04 12:38:50 +01:00
|
|
|
"vitest": "^4.0.18"
|
2024-07-29 15:06:59 +01:00
|
|
|
},
|
2024-09-02 15:23:46 +02:00
|
|
|
"packageManager": "pnpm@9.6.0",
|
|
|
|
|
"pnpm": {
|
|
|
|
|
"patchedDependencies": {
|
2026-03-18 15:57:52 +01:00
|
|
|
"@parcel/watcher@2.5.1": "patches/@parcel__watcher@2.5.1.patch",
|
|
|
|
|
"lightningcss@1.32.0": "patches/lightningcss@1.32.0.patch"
|
2024-09-02 15:23:46 +02:00
|
|
|
}
|
|
|
|
|
}
|
2024-03-05 14:23:26 +01:00
|
|
|
}
|
