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

76 lines
2.2 KiB
JSON
Raw Normal View History

introduce v4 codebase
2024-03-05 14:23:26 +01:00
{
"name": "@tailwindcss/oxide",
Release v4.1.18 (#19431)
2025-12-11 10:55:25 -05:00
"version": "4.1.18",
[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",
"url": "git+https://github.com/tailwindlabs/tailwindcss.git",
Hoist `oxide/crates` to just `crates` (#13333) * move `oxide/crates` to `crates` * ignore `target/` folder * ensure pnpm points to `crates` instead of `oxide/crates` * ensure all paths point to `crates` instead of `oxide/crates` * update `oxide/crates` -> `crates` path in workflows * use correct path in .prettierignore * rename `crates/core` to `crates/oxide` * remove oxide folder * fix test script to run `cargo test` directly
2024-03-23 14:00:48 +01:00
"directory": "crates/node"
[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
"main": "index.js",
"types": "index.d.ts",
"napi": {
Add experimental `@tailwindcss/oxide-wasm32-wasi` (#17558) Closes #17448 Closes #13133 This PR adds an a new Oxide target for `wasm32-wasip1-threads`: `@tailwindcss/oxide-wasm32-wasi`. The goal of this is to enable more environments to run Oxide, including (but not limited to) StackBlitz. We're making use of `napi-rs`'s upcoming v3 features to simplify the setup here, meaning `napi-rs` will configure the WASM target and create an npm package that works across Node and browser environments. ## MacOS AArch64 issues While setting up an integration test for the new WASM target, I ran into an issue where FS reads where not terminating on macOS. After some research I found this to be a limitation of the Node.js container interface right now, see: https://github.com/nodejs/node/issues/47193 ### Windows issues We also found that the Node.js wasi container does not properly support Windows: https://github.com/nodejs/uvwasi/issues/11 For now we, it's probably best for MacOS AArch64 users and Windows users to use the native modules instead. ## Test plan The `@tailwindcss/oxide-wasm32-wasi` npm package can be built locally via `pnpm build` and then run with the Oxide API. A usage example can be taken from the newly added integration test. Furthermore this was tested to work as a polyfill on StackBlitz: https://stackblitz.com/edit/vitejs-vite-uks3gt5p [ci-all] --------- Co-authored-by: Robin Malfait <malfait.robin@gmail.com>
2025-04-11 17:19:55 +02:00
"binaryName": "tailwindcss-oxide",
"packageName": "@tailwindcss/oxide",
"targets": [
"armv7-linux-androideabi",
"aarch64-linux-android",
"aarch64-apple-darwin",
"aarch64-unknown-linux-gnu",
"aarch64-unknown-linux-musl",
"armv7-unknown-linux-gnueabihf",
"x86_64-unknown-linux-musl",
"x86_64-unknown-freebsd",
"i686-pc-windows-msvc",
"aarch64-pc-windows-msvc",
"wasm32-wasip1-threads"
],
"wasm": {
"initialMemory": 16384,
"browser": {
"fs": true
}
introduce v4 codebase
2024-03-05 14:23:26 +01:00
}
},
"license": "MIT",
"devDependencies": {
pin `@napi-rs/cli` Newer versions of `@napi-rs/cli` (I noticed it in 3.5.1) rely on `@inquirer/core` for the CLI. This version requires a modern Node version because it relies on `import { styleText } from 'node:util';` which is not supported on older Node versions (<20). The issue now is that we rely on a Docker image on ghcr (ghcr.io/napi-rs/napi-rs/nodejs-rust:lts-alpine) which ships with Node v18 which is too old and would crash when trying to build on CI. Once ghcr is updated with a newer embedded Node version, we can bump `@napi-rs/cli` again. But for now, it's pinned.
2026-01-06 15:18:05 +01:00
"@napi-rs/cli": "3.4.1",
Update @napi-rs/wasm-runtime 1.1.0 → 1.1.1 (patch) (#19527) <!--depfu-start--> > 👉 **This PR is queued up to get rebased by Depfu** <!--depfu-end--> Here is everything you need to know about this update. Please take a good look at what changed and the test results before merging this pull request. ### What changed? #### ✳️ @​napi-rs/wasm-runtime (1.1.0 → 1.1.1) · [Repo](https://github.com/napi-rs/napi-rs) Sorry, we couldn't find anything useful about this release. --- ![Depfu Status](https://depfu.com/badges/edd6acd35d74c8d41cbb540c30442adf/stats.svg) [Depfu](https://depfu.com) will automatically keep this PR conflict-free, as long as you don't add any commits to this branch yourself. You can also trigger a rebase manually by commenting with `@depfu rebase`. <details><summary>All Depfu comment commands</summary> <blockquote><dl> <dt>@​depfu rebase</dt><dd>Rebases against your default branch and redoes this update</dd> <dt>@​depfu recreate</dt><dd>Recreates this PR, overwriting any edits that you've made to it</dd> <dt>@​depfu merge</dt><dd>Merges this PR once your tests are passing and conflicts are resolved</dd> <dt>@​depfu cancel merge</dt><dd>Cancels automatic merging of this PR</dd> <dt>@​depfu close</dt><dd>Closes this PR and deletes the branch</dd> <dt>@​depfu reopen</dt><dd>Restores the branch and reopens this PR (if it's closed)</dd> <dt>@​depfu pause</dt><dd>Ignores all future updates for this dependency and closes this PR</dd> <dt>@​depfu pause [minor|major]</dt><dd>Ignores all future minor/major updates for this dependency and closes this PR</dd> <dt>@​depfu resume</dt><dd>Future versions of this dependency will create PRs again (leaves this PR as is)</dd> </dl></blockquote> </details> Co-authored-by: depfu[bot] <23717796+depfu[bot]@users.noreply.github.com>
2026-01-06 11:49:41 +00:00
"@napi-rs/wasm-runtime": "^1.1.1",
Update emnapi 1.6.0 → 1.7.1 (minor) (#19351) Here is everything you need to know about this upgrade. Please take a good look at what changed and the test results before merging this pull request. ### What changed? #### ✳️ emnapi (1.6.0 → 1.7.1) · [Repo](https://github.com/toyobayashi/emnapi) <details> <summary>Release Notes</summary> <h4><a href="https://github.com/toyobayashi/emnapi/releases/tag/v1.7.1">1.7.1</a></h4> <blockquote><h2 dir="auto">What's Changed</h2> <ul dir="auto"> <li>move Node-API version detection by <a href="https://bounce.depfu.com/github.com/toyobayashi">@toyobayashi</a> in <a href="https://bounce.depfu.com/github.com/toyobayashi/emnapi/pull/182">#182</a> </li> <li>feat: support SharedArrayBuffer in napi_create_dataview by <a href="https://bounce.depfu.com/github.com/toyobayashi">@toyobayashi</a> in <a href="https://bounce.depfu.com/github.com/toyobayashi/emnapi/pull/183">#183</a> </li> </ul> <p dir="auto"><strong>Full Changelog</strong>: <a href="https://bounce.depfu.com/github.com/toyobayashi/emnapi/compare/v1.7.0...v1.7.1"><tt>v1.7.0...v1.7.1</tt></a></p></blockquote> <h4><a href="https://github.com/toyobayashi/emnapi/releases/tag/v1.7.0">1.7.0</a></h4> <blockquote><h2 dir="auto">What's Changed</h2> <ul dir="auto"> <li>feat: add napi_create_object_with_properties method by <a href="https://bounce.depfu.com/github.com/toyobayashi">@toyobayashi</a> in <a href="https://bounce.depfu.com/github.com/toyobayashi/emnapi/pull/181">#181</a> </li> </ul> <p dir="auto"><strong>Full Changelog</strong>: <a href="https://bounce.depfu.com/github.com/toyobayashi/emnapi/compare/v1.6.0...v1.7.0"><tt>v1.6.0...v1.7.0</tt></a></p></blockquote> <p><em>Does any of this look wrong? <a href="https://depfu.com/packages/npm/emnapi/feedback">Please let us know.</a></em></p> </details> <details> <summary>Commits</summary> <p><a href="https://github.com/toyobayashi/emnapi/compare/86d68f88ec3cc3949a555c93a633fa8997534413...f40577ad6013236e46bef57d829ece20773997bb">See the full diff on Github</a>. The new version differs by 6 commits:</p> <ul> <li><a href="https://github.com/toyobayashi/emnapi/commit/f40577ad6013236e46bef57d829ece20773997bb"><code>1.7.1</code></a></li> <li><a href="https://github.com/toyobayashi/emnapi/commit/c95f961fbcd33be46cdcc7ae77fb299c773a675a"><code>feat: support SharedArrayBuffer in napi_create_dataview (#183)</code></a></li> <li><a href="https://github.com/toyobayashi/emnapi/commit/92964e3738bd380c9c66bfc2cf8f332d108035f1"><code>move Node-API version detection (#182)</code></a></li> <li><a href="https://github.com/toyobayashi/emnapi/commit/11f4936f39121d0d79bc4901cf14dca02ef4abea"><code>1.7.0</code></a></li> <li><a href="https://github.com/toyobayashi/emnapi/commit/44bd3c798d97952d5dccc2fc9ab14494b9ef7964"><code>[Backport] feat: add napi_create_object_with_properties method (#181)</code></a></li> <li><a href="https://github.com/toyobayashi/emnapi/commit/62ab842b64f14da4a9838861758cbcb5c8465900"><code>ci: fix version retrieval</code></a></li> </ul> </details> --- ![Depfu Status](https://depfu.com/badges/edd6acd35d74c8d41cbb540c30442adf/stats.svg) [Depfu](https://depfu.com) will automatically keep this PR conflict-free, as long as you don't add any commits to this branch yourself. You can also trigger a rebase manually by commenting with `@depfu rebase`. <details><summary>All Depfu comment commands</summary> <blockquote><dl> <dt>@​depfu rebase</dt><dd>Rebases against your default branch and redoes this update</dd> <dt>@​depfu recreate</dt><dd>Recreates this PR, overwriting any edits that you've made to it</dd> <dt>@​depfu merge</dt><dd>Merges this PR once your tests are passing and conflicts are resolved</dd> <dt>@​depfu cancel merge</dt><dd>Cancels automatic merging of this PR</dd> <dt>@​depfu close</dt><dd>Closes this PR and deletes the branch</dd> <dt>@​depfu reopen</dt><dd>Restores the branch and reopens this PR (if it's closed)</dd> <dt>@​depfu pause</dt><dd>Ignores all future updates for this dependency and closes this PR</dd> <dt>@​depfu pause [minor|major]</dt><dd>Ignores all future minor/major updates for this dependency and closes this PR</dd> <dt>@​depfu resume</dt><dd>Future versions of this dependency will create PRs again (leaves this PR as is)</dd> </dl></blockquote> </details> Co-authored-by: depfu[bot] <23717796+depfu[bot]@users.noreply.github.com>
2025-11-21 09:41:20 -05:00
"emnapi": "1.7.1"
introduce v4 codebase
2024-03-05 14:23:26 +01:00
},
"engines": {
bump required engine to Node 20
2026-01-06 13:57:52 +01:00
"node": ">= 20"
introduce v4 codebase
2024-03-05 14:23:26 +01:00
},
"files": [
"index.js",
Remove Oxide postinstall script (#19149) This PR effectively reverts #17929. The bug in npm that required it was fixed a couple of months ago and with recent changes to pnpm that requires manually approving all postinstall scripts, this is creating some unnecessary noise.
2025-10-19 10:50:21 +02:00
"index.d.ts"
introduce v4 codebase
2024-03-05 14:23:26 +01:00
],
[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
"scripts": {
Add experimental `@tailwindcss/oxide-wasm32-wasi` (#17558) Closes #17448 Closes #13133 This PR adds an a new Oxide target for `wasm32-wasip1-threads`: `@tailwindcss/oxide-wasm32-wasi`. The goal of this is to enable more environments to run Oxide, including (but not limited to) StackBlitz. We're making use of `napi-rs`'s upcoming v3 features to simplify the setup here, meaning `napi-rs` will configure the WASM target and create an npm package that works across Node and browser environments. ## MacOS AArch64 issues While setting up an integration test for the new WASM target, I ran into an issue where FS reads where not terminating on macOS. After some research I found this to be a limitation of the Node.js container interface right now, see: https://github.com/nodejs/node/issues/47193 ### Windows issues We also found that the Node.js wasi container does not properly support Windows: https://github.com/nodejs/uvwasi/issues/11 For now we, it's probably best for MacOS AArch64 users and Windows users to use the native modules instead. ## Test plan The `@tailwindcss/oxide-wasm32-wasi` npm package can be built locally via `pnpm build` and then run with the Oxide API. A usage example can be taken from the newly added integration test. Furthermore this was tested to work as a polyfill on StackBlitz: https://stackblitz.com/edit/vitejs-vite-uks3gt5p [ci-all] --------- Co-authored-by: Robin Malfait <malfait.robin@gmail.com>
2025-04-11 17:19:55 +02:00
"build": "pnpm run build:platform && pnpm run build:wasm",
Bump napi toolchain to 3.3 (#18947) This PR bumps all napi related dependencies to their latest version. Napi 3 has by now officially been released but since we've been using the preview already, there aren't many changes. One thing that ChatGPT found is that `--no-const-enum` is the default behavior now (see default value [in this table](https://napi.rs/docs/cli/build#options)) ## Test plan - `pnpm install && pnpm build` - `cd crates/node/npm/wasm32-wasi` - `pnpm install --ignore-workspace` (This is necessary for some reason or the bundled dependencies won't work, I have no clue why it's not necessary on CI) - `pnpm pack` - Install dependency in a new npm package with a simple config like this: ```js import { Scanner } from "@tailwindcss/oxide-wasm32-wasi"; let scanner = new Scanner({ sources: [ { base: "/Users/philipp/dev/tailwindcss/packages/@tailwindcss-postcss/src/fixtures/example-project", pattern: "**/*", negated: false, }, ], }); console.log(scanner.scan()); ``` - <img width="904" height="494" alt="CleanShot 2025-09-19 at 14 53 52@2x" src="https://github.com/user-attachments/assets/93e32c19-6db4-4d00-9fdb-a6fde22fc69c" /> I also tested the CI build to make sure the `bundledDependencies` are properly added.
2025-09-19 17:08:41 +02:00
"build:platform": "napi build --platform --release",
Add experimental `@tailwindcss/oxide-wasm32-wasi` (#17558) Closes #17448 Closes #13133 This PR adds an a new Oxide target for `wasm32-wasip1-threads`: `@tailwindcss/oxide-wasm32-wasi`. The goal of this is to enable more environments to run Oxide, including (but not limited to) StackBlitz. We're making use of `napi-rs`'s upcoming v3 features to simplify the setup here, meaning `napi-rs` will configure the WASM target and create an npm package that works across Node and browser environments. ## MacOS AArch64 issues While setting up an integration test for the new WASM target, I ran into an issue where FS reads where not terminating on macOS. After some research I found this to be a limitation of the Node.js container interface right now, see: https://github.com/nodejs/node/issues/47193 ### Windows issues We also found that the Node.js wasi container does not properly support Windows: https://github.com/nodejs/uvwasi/issues/11 For now we, it's probably best for MacOS AArch64 users and Windows users to use the native modules instead. ## Test plan The `@tailwindcss/oxide-wasm32-wasi` npm package can be built locally via `pnpm build` and then run with the Oxide API. A usage example can be taken from the newly added integration test. Furthermore this was tested to work as a polyfill on StackBlitz: https://stackblitz.com/edit/vitejs-vite-uks3gt5p [ci-all] --------- Co-authored-by: Robin Malfait <malfait.robin@gmail.com>
2025-04-11 17:19:55 +02:00
"postbuild:platform": "node ./scripts/move-artifacts.mjs",
Bump napi toolchain to 3.3 (#18947) This PR bumps all napi related dependencies to their latest version. Napi 3 has by now officially been released but since we've been using the preview already, there aren't many changes. One thing that ChatGPT found is that `--no-const-enum` is the default behavior now (see default value [in this table](https://napi.rs/docs/cli/build#options)) ## Test plan - `pnpm install && pnpm build` - `cd crates/node/npm/wasm32-wasi` - `pnpm install --ignore-workspace` (This is necessary for some reason or the bundled dependencies won't work, I have no clue why it's not necessary on CI) - `pnpm pack` - Install dependency in a new npm package with a simple config like this: ```js import { Scanner } from "@tailwindcss/oxide-wasm32-wasi"; let scanner = new Scanner({ sources: [ { base: "/Users/philipp/dev/tailwindcss/packages/@tailwindcss-postcss/src/fixtures/example-project", pattern: "**/*", negated: false, }, ], }); console.log(scanner.scan()); ``` - <img width="904" height="494" alt="CleanShot 2025-09-19 at 14 53 52@2x" src="https://github.com/user-attachments/assets/93e32c19-6db4-4d00-9fdb-a6fde22fc69c" /> I also tested the CI build to make sure the `bundledDependencies` are properly added.
2025-09-19 17:08:41 +02:00
"build:wasm": "napi build --release --target wasm32-wasip1-threads",
Add experimental `@tailwindcss/oxide-wasm32-wasi` (#17558) Closes #17448 Closes #13133 This PR adds an a new Oxide target for `wasm32-wasip1-threads`: `@tailwindcss/oxide-wasm32-wasi`. The goal of this is to enable more environments to run Oxide, including (but not limited to) StackBlitz. We're making use of `napi-rs`'s upcoming v3 features to simplify the setup here, meaning `napi-rs` will configure the WASM target and create an npm package that works across Node and browser environments. ## MacOS AArch64 issues While setting up an integration test for the new WASM target, I ran into an issue where FS reads where not terminating on macOS. After some research I found this to be a limitation of the Node.js container interface right now, see: https://github.com/nodejs/node/issues/47193 ### Windows issues We also found that the Node.js wasi container does not properly support Windows: https://github.com/nodejs/uvwasi/issues/11 For now we, it's probably best for MacOS AArch64 users and Windows users to use the native modules instead. ## Test plan The `@tailwindcss/oxide-wasm32-wasi` npm package can be built locally via `pnpm build` and then run with the Oxide API. A usage example can be taken from the newly added integration test. Furthermore this was tested to work as a polyfill on StackBlitz: https://stackblitz.com/edit/vitejs-vite-uks3gt5p [ci-all] --------- Co-authored-by: Robin Malfait <malfait.robin@gmail.com>
2025-04-11 17:19:55 +02:00
"postbuild:wasm": "node ./scripts/move-artifacts.mjs",
introduce v4 codebase
2024-03-05 14:23:26 +01:00
"dev": "cargo watch --quiet --shell 'npm run build'",
Bump napi toolchain to 3.3 (#18947) This PR bumps all napi related dependencies to their latest version. Napi 3 has by now officially been released but since we've been using the preview already, there aren't many changes. One thing that ChatGPT found is that `--no-const-enum` is the default behavior now (see default value [in this table](https://napi.rs/docs/cli/build#options)) ## Test plan - `pnpm install && pnpm build` - `cd crates/node/npm/wasm32-wasi` - `pnpm install --ignore-workspace` (This is necessary for some reason or the bundled dependencies won't work, I have no clue why it's not necessary on CI) - `pnpm pack` - Install dependency in a new npm package with a simple config like this: ```js import { Scanner } from "@tailwindcss/oxide-wasm32-wasi"; let scanner = new Scanner({ sources: [ { base: "/Users/philipp/dev/tailwindcss/packages/@tailwindcss-postcss/src/fixtures/example-project", pattern: "**/*", negated: false, }, ], }); console.log(scanner.scan()); ``` - <img width="904" height="494" alt="CleanShot 2025-09-19 at 14 53 52@2x" src="https://github.com/user-attachments/assets/93e32c19-6db4-4d00-9fdb-a6fde22fc69c" /> I also tested the CI build to make sure the `bundledDependencies` are properly added.
2025-09-19 17:08:41 +02:00
"build:debug": "napi build --platform",
Remove Oxide postinstall script (#19149) This PR effectively reverts #17929. The bug in npm that required it was fixed a couple of months ago and with recent changes to pnpm that requires manually approving all postinstall scripts, this is creating some unnecessary noise.
2025-10-19 10:50:21 +02:00
"version": "napi version"
introduce v4 codebase
2024-03-05 14:23:26 +01:00
},
"optionalDependencies": {
[v4] Android binaries for Oxide (#13115)
2024-03-08 20:08:24 +03:00
"@tailwindcss/oxide-android-arm64": "workspace:*",
introduce v4 codebase
2024-03-05 14:23:26 +01:00
"@tailwindcss/oxide-darwin-arm64": "workspace:*",
"@tailwindcss/oxide-darwin-x64": "workspace:*",
"@tailwindcss/oxide-freebsd-x64": "workspace:*",
"@tailwindcss/oxide-linux-arm-gnueabihf": "workspace:*",
"@tailwindcss/oxide-linux-arm64-gnu": "workspace:*",
"@tailwindcss/oxide-linux-arm64-musl": "workspace:*",
"@tailwindcss/oxide-linux-x64-gnu": "workspace:*",
"@tailwindcss/oxide-linux-x64-musl": "workspace:*",
Add experimental `@tailwindcss/oxide-wasm32-wasi` (#17558) Closes #17448 Closes #13133 This PR adds an a new Oxide target for `wasm32-wasip1-threads`: `@tailwindcss/oxide-wasm32-wasi`. The goal of this is to enable more environments to run Oxide, including (but not limited to) StackBlitz. We're making use of `napi-rs`'s upcoming v3 features to simplify the setup here, meaning `napi-rs` will configure the WASM target and create an npm package that works across Node and browser environments. ## MacOS AArch64 issues While setting up an integration test for the new WASM target, I ran into an issue where FS reads where not terminating on macOS. After some research I found this to be a limitation of the Node.js container interface right now, see: https://github.com/nodejs/node/issues/47193 ### Windows issues We also found that the Node.js wasi container does not properly support Windows: https://github.com/nodejs/uvwasi/issues/11 For now we, it's probably best for MacOS AArch64 users and Windows users to use the native modules instead. ## Test plan The `@tailwindcss/oxide-wasm32-wasi` npm package can be built locally via `pnpm build` and then run with the Oxide API. A usage example can be taken from the newly added integration test. Furthermore this was tested to work as a polyfill on StackBlitz: https://stackblitz.com/edit/vitejs-vite-uks3gt5p [ci-all] --------- Co-authored-by: Robin Malfait <malfait.robin@gmail.com>
2025-04-11 17:19:55 +02:00
"@tailwindcss/oxide-wasm32-wasi": "workspace:*",
"@tailwindcss/oxide-win32-arm64-msvc": "workspace:*",
"@tailwindcss/oxide-win32-x64-msvc": "workspace:*"
introduce v4 codebase
2024-03-05 14:23:26 +01:00
}
}
Reference in a new issue Copy permalink