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

42 lines
1 KiB
JSON
Raw Normal View History

Move the CLI to its own package `@tailwindcss/cli` (#13095) * move `cli` to its own package `@tailwindcss/cli` * minify builds when using `tsup` * prefer tsup cli flag over tsup.config.ts file * add `--clean`, to make sure `dist/` folders are cleaned before building * make CLI esm only * use version of `tailwindcss` instead of the version of `@tailwindcss/cli`
2024-03-06 11:41:12 +01:00
{
"name": "@tailwindcss/cli",
Prepare v4.0.0-beta.4 (#15245)
2024-11-29 17:18:42 +01:00
"version": "4.0.0-beta.4",
Move the CLI to its own package `@tailwindcss/cli` (#13095) * move `cli` to its own package `@tailwindcss/cli` * minify builds when using `tsup` * prefer tsup cli flag over tsup.config.ts file * add `--clean`, to make sure `dist/` folders are cleaned before building * make CLI esm only * use version of `tailwindcss` instead of the version of `@tailwindcss/cli`
2024-03-06 11:41:12 +01:00
"description": "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-cli"
},
Move the CLI to its own package `@tailwindcss/cli` (#13095) * move `cli` to its own package `@tailwindcss/cli` * minify builds when using `tsup` * prefer tsup cli flag over tsup.config.ts file * add `--clean`, to make sure `dist/` folders are cleaned before building * make CLI esm only * use version of `tailwindcss` instead of the version of `@tailwindcss/cli`
2024-03-06 11:41:12 +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",
Move the CLI to its own package `@tailwindcss/cli` (#13095) * move `cli` to its own package `@tailwindcss/cli` * minify builds when using `tsup` * prefer tsup cli flag over tsup.config.ts file * add `--clean`, to make sure `dist/` folders are cleaned before building * make CLI esm only * use version of `tailwindcss` instead of the version of `@tailwindcss/cli`
2024-03-06 11:41:12 +01:00
"dev": "pnpm run build -- --watch"
},
"bin": {
"tailwindcss": "./dist/index.mjs"
},
"exports": {
"./package.json": "./package.json"
},
"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
},
Move the CLI to its own package `@tailwindcss/cli` (#13095) * move `cli` to its own package `@tailwindcss/cli` * minify builds when using `tsup` * prefer tsup cli flag over tsup.config.ts file * add `--clean`, to make sure `dist/` folders are cleaned before building * make CLI esm only * use version of `tailwindcss` instead of the version of `@tailwindcss/cli`
2024-03-06 11:41:12 +01:00
"dependencies": {
Upgrade `@parcel/watcher` to `2.5.0` (#14978) This PR upgrades parcel watcher to 2.5.0. Closes #14957 Closes #14958 Closes #14969 Closes #14970 Closes #14971
2024-11-13 11:38:43 +01:00
"@parcel/watcher": "^2.5.0",
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:^",
Move the CLI to its own package `@tailwindcss/cli` (#13095) * move `cli` to its own package `@tailwindcss/cli` * minify builds when using `tsup` * prefer tsup cli flag over tsup.config.ts file * add `--clean`, to make sure `dist/` folders are cleaned before building * make CLI esm only * use version of `tailwindcss` instead of the version of `@tailwindcss/cli`
2024-03-06 11:41:12 +01:00
"@tailwindcss/oxide": "workspace:^",
Add standalone CLI (#14270) This PR adds a new standalone client: A single-binary file that you can use to run Tailwind v4 without having a node setup. To make this work we use Bun's single-binary build which can properly package up native modules and the bun runtime for us so we do not have to rely on any expand-into-tmp-folder-at-runtime workarounds. When running locally, `pnpm build` will now standalone artifacts inside `packages/@tailwindcss-standalone/dist`. Note that since we do not build Oxide for other environments in the local setup, you won't be able to use the standalone artifacts for other platforms in local dev mode. Unfortunately Bun does not have support for Windows ARM builds yet but we found that using the `bun-baseline` runtime for Windows x64 would make the builds work fine in ARM emulation mode: ![Screenshot windows](https://github.com/user-attachments/assets/5b39387f-ec50-4757-9469-19b98e43162d) Some Bun related issues we faced and worked around: - We found that the regular Windows x64 build of `bun` does not run on Windows ARM via emulation. Instead, we have to use the `bun-baseline` builds which emulate correctly. - When we tried to bundle artifacts with [embed directories](https://bun.sh/docs/bundler/executables#embed-directories), node binary dependencies were no longer resolved correctly even though they would still be bundled and accessible within the [`embeddedFiles` list](https://bun.sh/docs/bundler/executables#listing-embedded-files). We worked around this by using the `import * as from ... with { type: "file" };` and patching the resolver we use in our CLI. - If you have an import to a module that is used as a regular import _and_ a `with { type: "file" }`, it will either return the module in both cases _or_ the file path when we would expect only the `with { type: "file" }` import to return the path. We do read the Tailwind CSS version via the file system and `require.resolve()` in the CLI and via `import * from './package.json'` in core and had to work around this by patching the version resolution in our CLI. ```ts import packageJson from "./package.json" import packageJsonPath from "./package.json" with {type: "file"} // We do not expect these to be equal packageJson === packageJsonPath ``` - We can not customize the app icon used for Windows `.exe` builds without decompiling the binary. For now we will leave the default but one workaround is to [use tools like ResourceHacker](https://github.com/tailwindlabs/tailwindcss/pull/14270/commits/698d9c4bd182391adb4b236f19a539aff13f78f9) to decompile the binary first. --------- Co-authored-by: Jordan Pittman <jordan@cryptica.me> Co-authored-by: Robin Malfait <malfait.robin@gmail.com>
2024-09-02 15:23:46 +02:00
"enhanced-resolve": "^5.17.1",
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:",
Move the CLI to its own package `@tailwindcss/cli` (#13095) * move `cli` to its own package `@tailwindcss/cli` * minify builds when using `tsup` * prefer tsup cli flag over tsup.config.ts file * add `--clean`, to make sure `dist/` folders are cleaned before building * make CLI esm only * use version of `tailwindcss` instead of the version of `@tailwindcss/cli`
2024-03-06 11:41:12 +01:00
"mri": "^1.2.0",
Update picocolors 1.0.1 → 1.1.1 (minor) (#14771)
2024-10-24 11:25:50 +02:00
"picocolors": "^1.1.1",
Ensure clients pin the `tailwindcss` version (#15011) We noticed that in the current alpha 34 release, the `package.json` file of the `@tailwindcss/node` package only defines `tailwindcss` as a dev dependency. This makes it very easy for version mismatches to happen when a v3 version (or an earlier v4 alpha for that matter) was installed in the same project: ```json { "name": "@tailwindcss/node", "version": "4.0.0-alpha.34", "description": "A utility-first CSS framework for rapidly building custom user interfaces.", "license": "MIT", "repository": { "type": "git", "url": "https://github.com/tailwindlabs/tailwindcss.git", "directory": "packages/@tailwindcss-node" }, "bugs": "https://github.com/tailwindlabs/tailwindcss/issues", "homepage": "https://tailwindcss.com", "files": [ "dist/" ], "publishConfig": { "provenance": true, "access": "public" }, "exports": { ".": { "types": "./dist/index.d.ts", "import": "./dist/index.mjs", "require": "./dist/index.js" }, "./require-cache": { "types": "./dist/require-cache.d.ts", "default": "./dist/require-cache.js" }, "./esm-cache-loader": { "types": "./dist/esm-cache.loader.d.mts", "default": "./dist/esm-cache.loader.mjs" } }, "devDependencies": { "tailwindcss": "4.0.0-alpha.34" }, "dependencies": { "enhanced-resolve": "^5.17.1", "jiti": "^2.0.0-beta.3" }, "scripts": { "build": "tsup-node", "dev": "pnpm run build -- --watch" } } ``` Furthermore, we were trying to fix issues where our integration test setup could not install `tailwindcss@3` because of how we did pnpm overrides. This PR fixes this by: - Ensuring every client that calls into `tailwindcss` core marks it as a version-pinned dependency. You are still required to install `tailwindcss` in your project along side a client (e.g. `@tailwindcss/vite`) but we now only use your installed version for importing the respective `.css` files. For the core logic, we are now requiring each package to use `tailwindcss` at the same version. This should help resolve issues like https://github.com/tailwindlabs/tailwindcss/discussions/14652 - We tried to eliminate the dependency on `tailwindcss` from the `@tailwindcss/upgrade` package. Unfortunately this is not possible to do right now because we need to load the CSS files from v4 to create the right environment. In a future version we could bundle the required CSS files with `@tailwidncss/upgrade` but it doesn't seem necessary for now. - We then changed our integration test overrides to only override the `tailwindcss` package that are dependencies of the known list of packages that we have `tailwindcss` dependencies on: `@tailwindcss/node` and `@tailwindcss/upgrade`. This ensures that we can install v3 of `tailwindcss` in the integration tests and it will work. Something we want to do for some upgrade tests. # Test plan Integration work again. Furthermore we added a quick setup with the CLI using the local tarballs and ensured it works: ```bash pnpm init pnpm install ../../tailwindcss/dist/tailwindcss-cli.tgz pnpm install ../../tailwindcss/dist/tailwindcss.tgz echo '@import "tailwindcss";' > index.css echo '<div class="underline"></div>' > index.html pnpm tailwindcss -i index.css -o out.css cat out.css ```
2024-11-15 17:18:48 +01:00
"tailwindcss": "workspace:*"
Move the CLI to its own package `@tailwindcss/cli` (#13095) * move `cli` to its own package `@tailwindcss/cli` * minify builds when using `tsup` * prefer tsup cli flag over tsup.config.ts file * add `--clean`, to make sure `dist/` folders are cleaned before building * make CLI esm only * use version of `tailwindcss` instead of the version of `@tailwindcss/cli`
2024-03-06 11:41:12 +01:00
}
}
Reference in a new issue Copy permalink