tailwindcss/integrations/postcss-cli/package.json

{
  "name": "postcss-cli",
  "private": true,
  "version": "0.0.0",
  "scripts": {
    "build": "NODE_ENV=production postcss ./src/index.css -o ./dist/main.css",
    "test": "jest --runInBand"
  },
  "jest": {
    "displayName": "PostCSS CLI",
    "setupFilesAfterEnv": [
      "<rootDir>/../../jest/customMatchers.js"
    ]
  },
  "devDependencies": {
    "postcss": "^8.2.15",
    "postcss-cli": "^8.3.1"
  }
}
Integrations setup (#4354) * add integration test tools * setup jest in the integrations folder * add `test:integrations` script The default `npm test` script will ignore all the tests in the `integrations` folder. * add integration tests with `webpack 5` * add integration tests with `postcss-cli` * add `npm run install:integrations` script This script will run `npm install` in every integration, and in the integrations folder itself (to setup Jest for example). * add `toIncludeCss` custom matcher * increate Jest timeout for integration tests * add integration tests with `vite` * add integration tests with `webpack 4` * add isomorphic fetch * add the ability to wait for specific stdout/stderr output * write vite tests, assert using API calls We will wait for the correct stdout/stderr output, once we know that we can request the fresh css, we will fetch it and make assertions accordingly. Port is currently hardcoded, maybe we should use a packaage to ensure that we use a free port. * add integration tests with `rollup` * add integration tests with `parcel` * run all integration tests in band * add .gitignore in integrations folder 2021-05-18 17:21:35 +02:00			`{`
			`"name": "postcss-cli",`
			`"private": true,`
			`"version": "0.0.0",`
			`"scripts": {`
			`"build": "NODE_ENV=production postcss ./src/index.css -o ./dist/main.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			`"test": "jest --runInBand"`
Integrations setup (#4354) * add integration test tools * setup jest in the integrations folder * add `test:integrations` script The default `npm test` script will ignore all the tests in the `integrations` folder. * add integration tests with `webpack 5` * add integration tests with `postcss-cli` * add `npm run install:integrations` script This script will run `npm install` in every integration, and in the integrations folder itself (to setup Jest for example). * add `toIncludeCss` custom matcher * increate Jest timeout for integration tests * add integration tests with `vite` * add integration tests with `webpack 4` * add isomorphic fetch * add the ability to wait for specific stdout/stderr output * write vite tests, assert using API calls We will wait for the correct stdout/stderr output, once we know that we can request the fresh css, we will fetch it and make assertions accordingly. Port is currently hardcoded, maybe we should use a packaage to ensure that we use a free port. * add integration tests with `rollup` * add integration tests with `parcel` * run all integration tests in band * add .gitignore in integrations folder 2021-05-18 17:21:35 +02:00			`},`
			`"jest": {`
			`"displayName": "PostCSS CLI",`
			`"setupFilesAfterEnv": [`
			`"<rootDir>/../../jest/customMatchers.js"`
			`]`
			`},`
			`"devDependencies": {`
			`"postcss": "^8.2.15",`
			`"postcss-cli": "^8.3.1"`
			`}`
			`}`