wrapper/tailwindcss
1
0
Fork 0
Code Issues Pull requests Projects Releases 1 Packages Wiki Activity Actions
tailwindcss/package.json

114 lines
3.1 KiB
JSON
Raw Normal View History

Init
2017-07-20 08:38:55 -04:00
{
"name": "tailwindcss",
3.1.6
2022-07-11 15:56:46 -04:00
"version": "3.1.6",
Update package.json
2017-10-31 22:21:12 -04:00
"description": "A utility-first CSS framework for rapidly building custom user interfaces.",
Init
2017-07-20 08:38:55 -04:00
"license": "MIT",
update project entry point
2017-08-28 15:02:50 -05:00
"main": "lib/index.js",
Re-enable new features This reverts commits 1456ed9021b3455dbb4458c2fb7d8ab66dfb3fed, d0269c24b3c7ad4557b7e3f2779bd15c5ac501f7, and 57699a04036c542d82e7b7102d775d4d2379493d.
2022-04-12 14:12:01 -04:00
"types": "types/index.d.ts",
chore(package.json): tailwindcss->tailwindlabs (#2277)
2020-09-02 21:37:50 +03:00
"repository": "https://github.com/tailwindlabs/tailwindcss.git",
"bugs": "https://github.com/tailwindlabs/tailwindcss/issues",
Update package.json
2017-10-31 22:21:12 -04:00
"homepage": "https://tailwindcss.com",
Add command to process with tailwind from file with custom json config
2017-08-27 23:07:55 -05:00
"bin": {
Don't compile CLI Need to figure out which dependencies are platform specific before it's safe to do this.
2021-05-20 13:49:15 -04:00
"tailwind": "lib/cli.js",
"tailwindcss": "lib/cli.js"
Add command to process with tailwind from file with custom json config
2017-08-27 23:07:55 -05:00
},
Restructure and add build process
2017-08-25 16:02:12 -05:00
"scripts": {
Add TypeScript types for the `tailwind.config.js` file (#7891) * add generate-types script This script will generate the full list of core plugins, which will allow you to get code completion for the `corePlugins` section. It will also generate all the colors (and deprecated colors) which is used in multiple places in the config. * add types for the `tailwind.config.js` config file * annotate stubs with a JSDoc pointing to the types * add types to package.json - Updated the files to make sure that the types are being published - Add a `types` section in the `package.json`, otherwise your editor by default will look for the `DefinitelyTyped` types which got me really confused for a second. - Added some scripts to make sure that the generation of types happens when needed (before tests and before building). This way you never ever have to think about generating them when working on Tailwind CSS internals. * re-export types top-level Having a `colors.d.ts` next to the `colors.js` file allows us to type the `colors.js` file and your editor will pickup the types from `colors.d.ts`. * also publish generated types * update changelog * enable TypeScript only when using `init --types` for now * update tests to verify that `--types` works
2022-03-22 10:24:28 +01:00
"preswcify": "npm run generate && rimraf lib",
Switch to swc from babel (#5593) * refactor: switch to swc from babel * bump to latest versions of swc Co-authored-by: Sachin Raja <sachinraja2349@gmail.com>
2021-09-24 19:17:19 +02:00
"swcify": "swc src --out-dir lib --copy-files",
bundle cli peer dependencies with esbuild (#5595)
2021-09-24 18:57:17 -07:00
"postswcify": "esbuild lib/cli-peer-dependencies.js --bundle --platform=node --outfile=peers/index.js",
Switch to swc from babel (#5593) * refactor: switch to swc from babel * bump to latest versions of swc Co-authored-by: Sachin Raja <sachinraja2349@gmail.com>
2021-09-24 19:17:19 +02:00
"rebuild-fixtures": "npm run swcify && node -r @swc/register scripts/rebuildFixtures.js",
"prepublishOnly": "npm install --force && npm run swcify",
fix eslint issues
2017-11-04 01:32:25 -05:00
"style": "eslint .",
Add TypeScript types for the `tailwind.config.js` file (#7891) * add generate-types script This script will generate the full list of core plugins, which will allow you to get code completion for the `corePlugins` section. It will also generate all the colors (and deprecated colors) which is used in multiple places in the config. * add types for the `tailwind.config.js` config file * annotate stubs with a JSDoc pointing to the types * add types to package.json - Updated the files to make sure that the types are being published - Add a `types` section in the `package.json`, otherwise your editor by default will look for the `DefinitelyTyped` types which got me really confused for a second. - Added some scripts to make sure that the generation of types happens when needed (before tests and before building). This way you never ever have to think about generating them when working on Tailwind CSS internals. * re-export types top-level Having a `colors.d.ts` next to the `colors.js` file allows us to type the `colors.js` file and your editor will pickup the types from `colors.d.ts`. * also publish generated types * update changelog * enable TypeScript only when using `init --types` for now * update tests to verify that `--types` works
2022-03-22 10:24:28 +01:00
"pretest": "npm run generate",
Remove the watching context (#6858) * remove watching context * update changelog
2022-01-03 17:45:31 +01:00
"test": "jest",
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
"test:integrations": "npm run test --prefix ./integrations",
"install:integrations": "node scripts/install-integrations.js",
Only run coverage in CI
2020-11-19 12:39:00 -05:00
"posttest": "npm run style",
Add TypeScript types for the `tailwind.config.js` file (#7891) * add generate-types script This script will generate the full list of core plugins, which will allow you to get code completion for the `corePlugins` section. It will also generate all the colors (and deprecated colors) which is used in multiple places in the config. * add types for the `tailwind.config.js` config file * annotate stubs with a JSDoc pointing to the types * add types to package.json - Updated the files to make sure that the types are being published - Add a `types` section in the `package.json`, otherwise your editor by default will look for the `DefinitelyTyped` types which got me really confused for a second. - Added some scripts to make sure that the generation of types happens when needed (before tests and before building). This way you never ever have to think about generating them when working on Tailwind CSS internals. * re-export types top-level Having a `colors.d.ts` next to the `colors.js` file allows us to type the `colors.js` file and your editor will pickup the types from `colors.d.ts`. * also publish generated types * update changelog * enable TypeScript only when using `init --types` for now * update tests to verify that `--types` works
2022-03-22 10:24:28 +01:00
"generate:plugin-list": "node -r @swc/register scripts/create-plugin-list.js",
"generate:types": "node -r @swc/register scripts/generate-types.js",
Re-enable new features This reverts commits 1456ed9021b3455dbb4458c2fb7d8ab66dfb3fed, d0269c24b3c7ad4557b7e3f2779bd15c5ac501f7, and 57699a04036c542d82e7b7102d775d4d2379493d.
2022-04-12 14:12:01 -04:00
"generate": "npm run generate:plugin-list && npm run generate:types"
Restructure and add build process
2017-08-25 16:02:12 -05:00
},
Switch from npmignore to files option
2020-06-28 11:19:55 +02:00
"files": [
Update package `files` config (#5405)
2021-09-06 19:26:24 +01:00
"src/*",
Compile CLI to single file to avoid peer dependency issues
2021-05-14 17:02:15 -04:00
"cli/*",
Switch from npmignore to files option
2020-06-28 11:19:55 +02:00
"lib/*",
Improve new JIT-compatible CLI (#4558) Co-authored-by: Robin Malfait <malfait.robin@gmail.com>
2021-06-04 10:28:09 -04:00
"peers/*",
Switch from npmignore to files option
2020-06-28 11:19:55 +02:00
"scripts/*.js",
"stubs/*.stub.js",
Add `tailwindcss/nesting` plugin (#4673) * add nesting plugin * rename @tailwindcss/nesting to tailwindcss/nesting * ignore the built `nesting` plugin * add a postcss7 compat version * include `nesting` plugin when publishing * add `build-plugins` script This will allow us to keep the plugins in their dedicated folders + tests + postcss7 compatibility files. However, when we copy over the plugins to the root. For example `plugins/nesting/` -> `nesting/` we skip files like `.test.js` and `.postcss7.js`. * build plugins when running `prepublishOnly` * improve compat mode We will use a glob so that we can move all *.postcss7.* files to just *.* likewise we will also backup to *.* to *.postcss8.* for restoring purposes. Concrete example: - Current state: - index.js // PostCSS 8 implementation - index.postcss7.js // PostCSS 7 implementation - Run "compat" - index.js // PostCSS 7 implementation - index.postcss7.js // PostCSS 7 implementation - index.postcss8.js // PostCSS 8 implementation (Backup of original) - Run "compat:restore" - index.js // PostCSS 8 implementation - index.postcss7.js // PostCSS 7 implementation - X index.postcss8.js // PostCSS 8 implementation (Removed) * Update README.md * ensure we `npm install` before publishing Co-authored-by: Adam Wathan <adam.wathan@gmail.com>
2021-06-17 15:43:52 +02:00
"nesting/*",
Re-enable new features This reverts commits 1456ed9021b3455dbb4458c2fb7d8ab66dfb3fed, d0269c24b3c7ad4557b7e3f2779bd15c5ac501f7, and 57699a04036c542d82e7b7102d775d4d2379493d.
2022-04-12 14:12:01 -04:00
"types/**/*",
"*.d.ts",
Switch from npmignore to files option
2020-06-28 11:19:55 +02:00
"*.css",
"*.js"
],
Rework Babel setup to be more node-y less browser-y
2017-09-09 10:20:00 -04:00
"devDependencies": {
Update @swc/cli to version 0.1.57
2022-04-18 12:25:29 +00:00
"@swc/cli": "^0.1.57",
Update @swc/core to version 1.2.196
2022-06-01 21:25:37 +00:00
"@swc/core": "^1.2.196",
Update @swc/jest to version 0.2.21
2022-05-15 05:10:27 +00:00
"@swc/jest": "^0.2.21",
Update @swc/register to version 0.1.10
2022-02-03 05:55:45 +00:00
"@swc/register": "^0.1.10",
Update autoprefixer to version 10.4.7
2022-05-21 21:55:57 +00:00
"autoprefixer": "^10.4.7",
Update cssnano to version 5.1.12
2022-07-01 20:25:38 +00:00
"cssnano": "^5.1.12",
Update esbuild to version 0.14.48
2022-07-07 03:40:40 +00:00
"esbuild": "^0.14.48",
Update eslint to version 8.19.0
2022-07-15 20:57:46 +00:00
"eslint": "^8.19.0",
Update eslint-config-prettier to version 8.5.0
2022-03-19 10:56:04 +00:00
"eslint-config-prettier": "^8.5.0",
Update eslint-plugin-prettier to version 4.2.1
2022-07-07 02:26:23 +00:00
"eslint-plugin-prettier": "^4.2.1",
Update jest to version 28.1.2
2022-07-06 12:58:45 +00:00
"jest": "^28.1.2",
Update jest-diff to version 28.1.1
2022-06-14 06:26:54 +00:00
"jest-diff": "^28.1.1",
Update prettier to version 2.7.1
2022-06-21 07:41:45 +00:00
"prettier": "^2.7.1",
Update prettier-plugin-tailwindcss to version 0.1.12
2022-07-14 15:56:07 +00:00
"prettier-plugin-tailwindcss": "^0.1.12",
Preserve source maps for generated CSS (#7588) * Preserve source maps for `@apply` * Overwrite the source for all cloned descendants * Preserve source maps when expanding defaults * Verify that source maps are correctly generated * Update changelog
2022-02-23 11:24:54 -05:00
"rimraf": "^3.0.0",
"source-map-js": "^1.0.2"
Rework Babel setup to be more node-y less browser-y
2017-09-09 10:20:00 -04:00
},
Upgrade to PostCSS 8
2020-11-15 16:13:48 -05:00
"peerDependencies": {
"postcss": "^8.0.9"
},
Rework Babel setup to be more node-y less browser-y
2017-09-09 10:20:00 -04:00
"dependencies": {
Update arg to version 5.0.2
2022-06-12 18:40:31 +00:00
"arg": "^5.0.2",
Update chokidar to version 3.5.3
2022-01-25 07:55:59 +00:00
"chokidar": "^3.5.3",
Update color parsing and formatting (#5442) * Replace `culori` with simple color parser * Use space-separated color syntax * Update default color values to use space-separated syntax * Update separator regex * Fix tests * add tests for the new `color` util Also slightly modified the `color` util itself to take `transparent` into account and also format every value as a string for consistency. Co-authored-by: Robin Malfait <malfait.robin@gmail.com>
2021-09-09 15:15:53 +01:00
"color-name": "^1.1.4",
Update detective to version 5.2.1
2022-06-03 16:25:27 +00:00
"detective": "^5.2.1",
Update didyoumean to version 1.2.2
2021-07-01 14:14:46 +00:00
"didyoumean": "^1.2.2",
Copy JIT over, tests passing separately, not yet integrated
2021-04-02 11:16:15 -04:00
"dlv": "^1.1.3",
Update fast-glob to version 3.2.11
2022-01-16 13:56:00 +00:00
"fast-glob": "^3.2.11",
Update glob-parent to version 6.0.2
2021-10-06 22:26:01 +00:00
"glob-parent": "^6.0.2",
Update is-glob to version 4.0.3
2021-10-03 22:56:02 +00:00
"is-glob": "^4.0.3",
Update lilconfig to version 2.0.6
2022-07-17 13:55:43 +00:00
"lilconfig": "^2.0.6",
Copy JIT over, tests passing separately, not yet integrated
2021-04-02 11:16:15 -04:00
"normalize-path": "^3.0.0",
Update object-hash to version 3.0.0 (#7657) Co-authored-by: depfu[bot] <23717796+depfu[bot]@users.noreply.github.com>
2022-02-25 12:17:16 -05:00
"object-hash": "^3.0.0",
Replace chalk with picocolors (#6039) * Replace chalk with picocolors Already used in latest postcss, autoprefixer and browserslist versions. See https://github.com/alexeyraspopov/picocolors * Update `dim` function Co-authored-by: Brad Cornes <bradlc41@gmail.com>
2022-02-24 19:37:31 +03:00
"picocolors": "^1.0.0",
Update postcss to version 8.4.14
2022-05-28 01:11:05 +00:00
"postcss": "^8.4.14",
Add postcss-import support to the CLI (#8437) * Add postcss-import support to the CLI * Update changelog
2022-05-25 14:28:52 -04:00
"postcss-import": "^14.1.0",
Preserve case of css variables added by plugins (#6888)
2022-01-04 23:03:41 -05:00
"postcss-js": "^4.0.0",
Revert "Update postcss-load-config to version 4.0.1 (#8686)" This reverts commit c47e66613f1d1072f7a71278d2ebee090af3010c. Node 12 reached EOL on 30 April 2022 after which there will be no more bugfix or security releases. This is one reason why `postcss-load-config` dropped support for Node 10 *and* 12. However, as we still support Node 12 in Tailwind CSS v3, we can’t upgrade to `postcss-load-config` 4.0.
2022-07-11 10:00:10 -04:00
"postcss-load-config": "^3.1.4",
Update postcss-nested to version 5.0.6
2021-08-04 10:41:59 +00:00
"postcss-nested": "5.0.6",
Update postcss-selector-parser to version 6.0.10
2022-04-06 21:10:47 +00:00
"postcss-selector-parser": "^6.0.10",
Update postcss-value-parser to version 4.2.0
2021-12-06 11:57:26 +00:00
"postcss-value-parser": "^4.2.0",
Copy JIT over, tests passing separately, not yet integrated
2021-04-02 11:16:15 -04:00
"quick-lru": "^5.1.1",
Update resolve to version 1.22.1
2022-06-24 21:10:50 +00:00
"resolve": "^1.22.1"
Break Tailwind out into 3 private plugins, bake in cssnext and stylefmt
2017-08-26 11:18:50 -04:00
},
0.1.5
2017-11-08 08:36:56 -05:00
"browserslist": [
Update browserslist config for CDN builds
2020-10-21 21:09:31 -04:00
"> 1%",
Explicitly exclude pre-Chromium Edge from CDN builds The >1% was sometimes including this and other times not depending on CI vs. local, couldn't quite figure out why, guessing some difference in version of caniuse-lite.
2020-10-21 21:55:30 -04:00
"not edge <= 18",
Update browserslist config for CDN builds
2020-10-21 21:09:31 -04:00
"not ie 11",
"not op_mini all"
0.1.5
2017-11-08 08:36:56 -05:00
],
Generate focus variants as separate declarations
2017-11-22 15:52:32 -05:00
"jest": {
Increase test timeout
2020-10-18 15:37:42 -04:00
"testTimeout": 30000,
Lock postcss-nested to 5.0.1 Migrating to visitor API in 5.0.2 breaks a lot of things.
2021-04-02 13:46:33 -04:00
"setupFilesAfterEnv": [
"<rootDir>/jest/customMatchers.js"
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
],
Update postcss-selector-parser to version 6.0.6
2021-05-19 08:02:07 +00:00
"testPathIgnorePatterns": [
"/node_modules/",
Add standalone tailwindcss CLI (#6506) * Move standalone CLI into main repo * Update release tag * Update workflow * Ignore standalone CLI tests * Fix style * Update changelog [ci skip]
2021-12-14 12:12:06 -05:00
"/integrations/",
Skip tests ending in .test.skip.js
2022-06-01 06:16:39 -04:00
"/standalone-cli/",
"\\.test\\.skip\\.js$"
Switch to swc from babel (#5593) * refactor: switch to swc from babel * bump to latest versions of swc Co-authored-by: Sachin Raja <sachinraja2349@gmail.com>
2021-09-24 19:17:19 +02:00
],
"transform": {
"\\.js$": "@swc/jest"
}
Generate focus variants as separate declarations
2017-11-22 15:52:32 -05:00
},
Target node 6.9.0 Target the previous Node LTS instead of "whatever version of Node Adam is running today." 🤦🏻‍♂️
2017-11-01 18:01:29 -04:00
"engines": {
Drop support for Node.js 8 and 10, require 12.13 (#2582)
2020-10-16 13:12:32 -04:00
"node": ">=12.13.0"
Convert new stuff to use ES6 modules
2017-08-26 14:36:40 -05:00
}
Init
2017-07-20 08:38:55 -04:00
}
Reference in a new issue Copy permalink