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

47 lines
1.2 KiB
JSON
Raw Normal View History

introduce v4 codebase
2024-03-05 14:23:26 +01:00
{
"name": "@tailwindcss/postcss",
Prepare `v4.0.0-alpha.20` (#14244) Prepare next `4.0.0-alpha.20` release
2024-08-23 15:51:53 +02:00
"version": "4.0.0-alpha.20",
introduce v4 codebase
2024-03-05 14:23:26 +01:00
"description": "PostCSS plugin for Tailwind CSS, a utility-first CSS framework for rapidly building custom user interfaces",
"license": "MIT",
[v4] Add provenance to all published packages (#13160) * Add provenance to all packages Based on #13097 by @saibotk Add [provenance](https://docs.npmjs.com/generating-provenance-statements) for all published packages. --- Co-authored-by: saibotk <git@saibotk.de> * Document reason for id-token permission * Update changelog
2024-03-08 15:30:13 -05:00
"repository": {
"type": "git",
Correct repository fields in package.json files (#13416)
2024-03-31 21:20:53 +02:00
"url": "https://github.com/tailwindlabs/tailwindcss.git",
[v4] Add provenance to all published packages (#13160) * Add provenance to all packages Based on #13097 by @saibotk Add [provenance](https://docs.npmjs.com/generating-provenance-statements) for all published packages. --- Co-authored-by: saibotk <git@saibotk.de> * Document reason for id-token permission * Update changelog
2024-03-08 15:30:13 -05:00
"directory": "packages/@tailwindcss-postcss"
},
introduce v4 codebase
2024-03-05 14:23:26 +01:00
"bugs": "https://github.com/tailwindlabs/tailwindcss/issues",
"homepage": "https://tailwindcss.com",
"scripts": {
"lint": "tsc --noEmit",
Add `@source` support (#14078) This PR is an umbrella PR where we will add support for the new `@source` directive. This will allow you to add explicit content glob patterns if you want to look for Tailwind classes in other files that are not automatically detected yet. Right now this is an addition to the existing auto content detection that is automatically enabled in the `@tailwindcss/postcss` and `@tailwindcss/cli` packages. The `@tailwindcss/vite` package doesn't use the auto content detection, but uses the module graph instead. From an API perspective there is not a lot going on. There are only a few things that you have to know when using the `@source` directive, and you probably already know the rules: 1. You can use multiple `@source` directives if you want. 2. The `@source` accepts a glob pattern so that you can match multiple files at once 3. The pattern is relative to the current file you are in 4. The pattern includes all files it is matching, even git ignored files 1. The motivation for this is so that you can explicitly point to a `node_modules` folder if you want to look at `node_modules` for whatever reason. 6. Right now we don't support negative globs (starting with a `!`) yet, that will be available in the near future. Usage example: ```css /* ./src/input.css */ @import "tailwindcss"; @source "../laravel/resources/views/**/*.blade.php"; @source "../../packages/monorepo-package/**/*.js"; ``` It looks like the PR introduced a lot of changes, but this is a side effect of all the other plumbing work we had to do to make this work. For example: 1. We added dedicated integration tests that run on Linux and Windows in CI (just to make sure that all the `path` logic is correct) 2. We Have to make sure that the glob patterns are always correct even if you are using `@import` in your CSS and use `@source` in an imported file. This is because we receive the flattened CSS contents where all `@import`s are inlined. 3. We have to make sure that we also listen for changes in the files that match any of these patterns and trigger a rebuild. PRs: - [x] https://github.com/tailwindlabs/tailwindcss/pull/14063 - [x] https://github.com/tailwindlabs/tailwindcss/pull/14085 - [x] https://github.com/tailwindlabs/tailwindcss/pull/14079 - [x] https://github.com/tailwindlabs/tailwindcss/pull/14067 - [x] https://github.com/tailwindlabs/tailwindcss/pull/14076 - [x] https://github.com/tailwindlabs/tailwindcss/pull/14080 - [x] https://github.com/tailwindlabs/tailwindcss/pull/14127 - [x] https://github.com/tailwindlabs/tailwindcss/pull/14135 Once all the PRs are merged, then this umbrella PR can be merged. > [!IMPORTANT] > Make sure to merge this without rebasing such that each individual PR ends up on the main branch. --------- Co-authored-by: Philipp Spiess <hello@philippspiess.com> Co-authored-by: Jordan Pittman <jordan@cryptica.me> Co-authored-by: Adam Wathan <adam.wathan@gmail.com>
2024-08-07 16:38:44 +02:00
"build": "tsup-node",
introduce v4 codebase
2024-03-05 14:23:26 +01:00
"dev": "pnpm run build -- --watch"
},
"files": [
"dist/"
],
[v4] Add provenance to all published packages (#13160) * Add provenance to all packages Based on #13097 by @saibotk Add [provenance](https://docs.npmjs.com/generating-provenance-statements) for all published packages. --- Co-authored-by: saibotk <git@saibotk.de> * Document reason for id-token permission * Update changelog
2024-03-08 15:30:13 -05:00
"publishConfig": {
add `"access": "public"` to `publishConfig` (#13164)
2024-03-08 22:04:05 +01:00
"provenance": true,
"access": "public"
[v4] Add provenance to all published packages (#13160) * Add provenance to all packages Based on #13097 by @saibotk Add [provenance](https://docs.npmjs.com/generating-provenance-statements) for all published packages. --- Co-authored-by: saibotk <git@saibotk.de> * Document reason for id-token permission * Update changelog
2024-03-08 15:30:13 -05:00
},
introduce v4 codebase
2024-03-05 14:23:26 +01:00
"exports": {
".": {
"types": "./dist/index.d.ts",
Add ESM build of the `@tailwindcss/postcss` package (#13693) * Fixes exports when importing CJS form ESM file * Build a real ESM version of the postcss plugin --------- Co-authored-by: Jordan Pittman <jordan@cryptica.me>
2024-05-22 19:01:56 -04:00
"import": "./dist/index.mjs",
introduce v4 codebase
2024-03-05 14:23:26 +01:00
"require": "./dist/index.js"
}
},
"dependencies": {
Support loading config files via `@config` (#14239) In Tailwind v4 the CSS file is the main entry point to your project and is generally configured via `@theme`. However, given that all v3 projects were configured via a `tailwind.config.js` file we definitely need to support those. This PR adds support for loading existing Tailwind config files by adding an `@config` directive to the CSS — similar to how v3 supported multiple config files except that this is now _required_ to use a config file. You can load a config file like so: ``` @import "tailwindcss"; @config "./path/to/tailwind.config.js"; ``` A few notes: - Both CommonJS and ESM config files are supported (loaded directly via `import()` in Node) - This is not yet supported in Intellisense or Prettier — should hopefully land next week - TypeScript is **not yet** supported in the config file — this will be handled in a future PR. --------- Co-authored-by: Philipp Spiess <hello@philippspiess.com> Co-authored-by: Adam Wathan <adam.wathan@gmail.com> Co-authored-by: Robin Malfait <malfait.robin@gmail.com>
2024-09-02 12:03:16 -04:00
"@tailwindcss/node": "workspace:^",
introduce v4 codebase
2024-03-05 14:23:26 +01:00
"@tailwindcss/oxide": "workspace:^",
Bump dependencies (#14160) This PR bumps dependencies We also make some dependencies `catalog:` dependencies, which allows us to keep the version in sync. E.g.: `lightningcss` and `@types/node`. Bumped `turbo` to the latest version + enabled the new UI Fixed a bug in the tests now that `lightningcss` outputs the correct value.
2024-08-09 16:12:24 +02:00
"lightningcss": "catalog:",
Bump dependencies (#13738) * run `pnpm update --recursive` * update tests to reflect lightningcss bump It looks like it's mainly (re-)ordering properties. Not 100% sure why though.
2024-05-24 15:07:44 +02:00
"postcss-import": "^16.1.0",
introduce v4 codebase
2024-03-05 14:23:26 +01:00
"tailwindcss": "workspace:^"
},
"devDependencies": {
Upgrade vitest and remove bench script from CI (#14101) This PR updates vitest to v2. The changes are mostly around using fork instead of threads for how tests are run which should fix one of the issues we've found. Ever since adding the unit tests on Windows, we started seeing occacional flags of vitest crashing with the following error: ```  ELIFECYCLE  Command failed with exit code 3221225477. Error: Process completed with exit code 1. ``` When reading the [v2 changelog](https://github.com/vitest-dev/vitest/releases/tag/v2.0.0) we saw many bug fixes related to segfaulting so we believe this was the issue. When upgrading `vitest` alone, we got a bunch of dependency mismatches though (specifically, vite was installed two times with different peer dependencies for `@types/node` which causes our vite plugin's `Plugin` type to be different from the one in the vite playground. Yikes. These were eventually fixed by having pnpm create a new lockfile for us. So, unfortunatly this PR also bumps a bunch of patch versions for some transitive dependencies. Tests seem fine, though 🤞 This PR also removes the `bench` script from CI. It doesn't give us value in its current state (since it's not reporting when performance regresses) but added a few seconds of unnecessary overhead to each test run.
2024-08-02 10:33:14 +02:00
"@types/node": "catalog:",
introduce v4 codebase
2024-03-05 14:23:26 +01:00
"@types/postcss-import": "^14.0.3",
Bump dependencies (#14160) This PR bumps dependencies We also make some dependencies `catalog:` dependencies, which allows us to keep the version in sync. E.g.: `lightningcss` and `@types/node`. Bumped `turbo` to the latest version + enabled the new UI Fixed a bug in the tests now that `lightningcss` outputs the correct value.
2024-08-09 16:12:24 +02:00
"postcss": "^8.4.41",
Add `@source` support (#14078) This PR is an umbrella PR where we will add support for the new `@source` directive. This will allow you to add explicit content glob patterns if you want to look for Tailwind classes in other files that are not automatically detected yet. Right now this is an addition to the existing auto content detection that is automatically enabled in the `@tailwindcss/postcss` and `@tailwindcss/cli` packages. The `@tailwindcss/vite` package doesn't use the auto content detection, but uses the module graph instead. From an API perspective there is not a lot going on. There are only a few things that you have to know when using the `@source` directive, and you probably already know the rules: 1. You can use multiple `@source` directives if you want. 2. The `@source` accepts a glob pattern so that you can match multiple files at once 3. The pattern is relative to the current file you are in 4. The pattern includes all files it is matching, even git ignored files 1. The motivation for this is so that you can explicitly point to a `node_modules` folder if you want to look at `node_modules` for whatever reason. 6. Right now we don't support negative globs (starting with a `!`) yet, that will be available in the near future. Usage example: ```css /* ./src/input.css */ @import "tailwindcss"; @source "../laravel/resources/views/**/*.blade.php"; @source "../../packages/monorepo-package/**/*.js"; ``` It looks like the PR introduced a lot of changes, but this is a side effect of all the other plumbing work we had to do to make this work. For example: 1. We added dedicated integration tests that run on Linux and Windows in CI (just to make sure that all the `path` logic is correct) 2. We Have to make sure that the glob patterns are always correct even if you are using `@import` in your CSS and use `@source` in an imported file. This is because we receive the flattened CSS contents where all `@import`s are inlined. 3. We have to make sure that we also listen for changes in the files that match any of these patterns and trigger a rebuild. PRs: - [x] https://github.com/tailwindlabs/tailwindcss/pull/14063 - [x] https://github.com/tailwindlabs/tailwindcss/pull/14085 - [x] https://github.com/tailwindlabs/tailwindcss/pull/14079 - [x] https://github.com/tailwindlabs/tailwindcss/pull/14067 - [x] https://github.com/tailwindlabs/tailwindcss/pull/14076 - [x] https://github.com/tailwindlabs/tailwindcss/pull/14080 - [x] https://github.com/tailwindlabs/tailwindcss/pull/14127 - [x] https://github.com/tailwindlabs/tailwindcss/pull/14135 Once all the PRs are merged, then this umbrella PR can be merged. > [!IMPORTANT] > Make sure to merge this without rebasing such that each individual PR ends up on the main branch. --------- Co-authored-by: Philipp Spiess <hello@philippspiess.com> Co-authored-by: Jordan Pittman <jordan@cryptica.me> Co-authored-by: Adam Wathan <adam.wathan@gmail.com>
2024-08-07 16:38:44 +02:00
"internal-example-plugin": "workspace:*",
"internal-postcss-fix-relative-paths": "workspace:^"
introduce v4 codebase
2024-03-05 14:23:26 +01:00
}
}
Reference in a new issue Copy permalink