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

82 lines
2.4 KiB
JSON
Raw Permalink Normal View History

introduce v4 codebase
2024-03-05 14:23:26 +01:00
{
"name": "@tailwindcss/oxide",
Prepare v4.1.14 release (#19037) Co-authored-by: Robin Malfait <malfait.robin@gmail.com>
2025-10-01 11:48:02 -04:00
"version": "4.1.14",
[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",
Download platform specific package if `optionalDependencies` are skipped (#17929) Closes #15806 This PR adds a new `postinstall` script to `@tailwindcss/oxide` that will attempt to download the platform-specific optional dependency to avoid issues when the package manager does not do that automatically (see #15806). The implementation for this is fairly simple: The npm package is downloaded from the official npm servers and extracted into the `node_modules` directory of the `@tailwidncss/oxide` installation. ## Test plan Since we still lack a solid repro of #15806, the way I tested this change was to manually remove all automatically-installed optional dependencies and then running the postinstall script manually. The script then downloads the right version package which makes the import to `@tailwidncss/oxide` work. An appropriate integration test was added too. I furthermore also validated that: - This works across CI platforms [ci-all] - The postinstall script bails out when running `pnpm install` in the dev setup. This is necessary since doing the initial install won't have any binary dependencies yet so it would download invalid versions from npm (as the version numbers locally refer to the last released version). We can safely bail out here though since this was never an issue with local development. - The postinstall script does not do anything when the `@tailwindcss/oxide` library is added _unless_ the issue is detected. [ci-all] --------- Co-authored-by: Robin Malfait <malfait.robin@gmail.com>
2025-05-09 14:55:02 +02:00
"dependencies": {
Update tar 7.4.3 → 7.5.1 (minor) (#19035) 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? #### ✳️ tar (7.4.3 → 7.5.1) · [Repo](https://github.com/isaacs/node-tar) · [Changelog](https://github.com/isaacs/node-tar/blob/main/CHANGELOG.md) <details> <summary>Commits</summary> <p><a href="https://github.com/isaacs/node-tar/compare/206fcf91b01fae95ae859b8f3254bfd88744602a...64728e88cb5805faa78264204d520eb741ce4b6f">See the full diff on Github</a>. The new version differs by 21 commits:</p> <ul> <li><a href="https://github.com/isaacs/node-tar/commit/64728e88cb5805faa78264204d520eb741ce4b6f"><code>7.5.1</code></a></li> <li><a href="https://github.com/isaacs/node-tar/commit/5330eb04bc43014f216e5c271b40d5c00d45224d"><code>fix: consistent TOCTOU behavior in sync t.list</code></a></li> <li><a href="https://github.com/isaacs/node-tar/commit/dcb0287d7da925182aa8840ca1038bf44160ca5e"><code>7.5.0</code></a></li> <li><a href="https://github.com/isaacs/node-tar/commit/aa1bed928735d590d213770d4a3069ceecbfffa3"><code>changelog 7.5</code></a></li> <li><a href="https://github.com/isaacs/node-tar/commit/49bf8f9926f78c319cbeb1c26a7291284c41d2f4"><code>feat: add initial zstd support</code></a></li> <li><a href="https://github.com/isaacs/node-tar/commit/b35ff9474838fd05d039708d7011c469d9aca301"><code>ci: don&#39;t bother testing on node 18</code></a></li> <li><a href="https://github.com/isaacs/node-tar/commit/181be3a985cbe5371336da56745a55ea6b784cec"><code>update workflows, tshy configs</code></a></li> <li><a href="https://github.com/isaacs/node-tar/commit/15d4510393ef7c136d243ec09916d45779b90ad9"><code>7.4.4</code></a></li> <li><a href="https://github.com/isaacs/node-tar/commit/a4744652c379713d06a0ca30187f3d3456df5694"><code>Fix some typos</code></a></li> <li><a href="https://github.com/isaacs/node-tar/commit/65ff5bed156d851e32ccf13874c7c2e414fc2ace"><code>docs(changelog): add missing v7 breaking change</code></a></li> <li><a href="https://github.com/isaacs/node-tar/commit/458d0fd236f7a6eca8ad2bbe0456ba2b2473988f"><code>docs: clean up duplicate onwarn options</code></a></li> <li><a href="https://github.com/isaacs/node-tar/commit/afa8cf5e53e2efe9ad9c87bd7911a96a86d0604c"><code>update all deps</code></a></li> <li><a href="https://github.com/isaacs/node-tar/commit/bbfcec2e8b7896cfc7bf353fc924cfab688b4e93"><code>minizlib@3.1.0</code></a></li> <li><a href="https://github.com/isaacs/node-tar/commit/cdd4f7dced56f5b42939adafafb9f121b72729f0"><code>doc: fix lowlevel tar.Parser typo</code></a></li> <li><a href="https://github.com/isaacs/node-tar/commit/eafc4b8454c59ed3c31d53bb6601a34dd8bf3dfb"><code>remove yallist from parse, but NOT from pack</code></a></li> <li><a href="https://github.com/isaacs/node-tar/commit/d281312a94882a50bd0a3f3b26e41adb9f954dfa"><code>Use built-in mkdir instead of mkdirp</code></a></li> <li><a href="https://github.com/isaacs/node-tar/commit/0411fb11c491005046cb079e32b82973c89983d9"><code>format readme</code></a></li> <li><a href="https://github.com/isaacs/node-tar/commit/d5f986a516451b9d3c3cb6f39163efdd80946db5"><code>limit normalize-unicode cache size</code></a></li> <li><a href="https://github.com/isaacs/node-tar/commit/e79814eaf3c96427767f7ecc069538341a0c6041"><code>remove dirCache from mkdir, unpack</code></a></li> <li><a href="https://github.com/isaacs/node-tar/commit/d3cd4392d4a35a8f1e10287a07e57da6ae079e78"><code>remove extraneous &#39;for example&#39;</code></a></li> <li><a href="https://github.com/isaacs/node-tar/commit/02f883aa4d3336c023fb826d4ba11dde01c7f338"><code>docs on how to use onWriteEntry</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-09-30 14:53:29 -04:00
"tar": "^7.5.1",
Download platform specific package if `optionalDependencies` are skipped (#17929) Closes #15806 This PR adds a new `postinstall` script to `@tailwindcss/oxide` that will attempt to download the platform-specific optional dependency to avoid issues when the package manager does not do that automatically (see #15806). The implementation for this is fairly simple: The npm package is downloaded from the official npm servers and extracted into the `node_modules` directory of the `@tailwidncss/oxide` installation. ## Test plan Since we still lack a solid repro of #15806, the way I tested this change was to manually remove all automatically-installed optional dependencies and then running the postinstall script manually. The script then downloads the right version package which makes the import to `@tailwidncss/oxide` work. An appropriate integration test was added too. I furthermore also validated that: - This works across CI platforms [ci-all] - The postinstall script bails out when running `pnpm install` in the dev setup. This is necessary since doing the initial install won't have any binary dependencies yet so it would download invalid versions from npm (as the version numbers locally refer to the last released version). We can safely bail out here though since this was never an issue with local development. - The postinstall script does not do anything when the `@tailwindcss/oxide` library is added _unless_ the issue is detected. [ci-all] --------- Co-authored-by: Robin Malfait <malfait.robin@gmail.com>
2025-05-09 14:55:02 +02:00
"detect-libc": "^2.0.4"
},
introduce v4 codebase
2024-03-05 14:23:26 +01:00
"devDependencies": {
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
"@napi-rs/cli": "^3.2.0",
"@napi-rs/wasm-runtime": "^1.0.5",
"emnapi": "1.5.0"
introduce v4 codebase
2024-03-05 14:23:26 +01:00
},
"engines": {
"node": ">= 10"
},
"files": [
"index.js",
Download platform specific package if `optionalDependencies` are skipped (#17929) Closes #15806 This PR adds a new `postinstall` script to `@tailwindcss/oxide` that will attempt to download the platform-specific optional dependency to avoid issues when the package manager does not do that automatically (see #15806). The implementation for this is fairly simple: The npm package is downloaded from the official npm servers and extracted into the `node_modules` directory of the `@tailwidncss/oxide` installation. ## Test plan Since we still lack a solid repro of #15806, the way I tested this change was to manually remove all automatically-installed optional dependencies and then running the postinstall script manually. The script then downloads the right version package which makes the import to `@tailwidncss/oxide` work. An appropriate integration test was added too. I furthermore also validated that: - This works across CI platforms [ci-all] - The postinstall script bails out when running `pnpm install` in the dev setup. This is necessary since doing the initial install won't have any binary dependencies yet so it would download invalid versions from npm (as the version numbers locally refer to the last released version). We can safely bail out here though since this was never an issue with local development. - The postinstall script does not do anything when the `@tailwindcss/oxide` library is added _unless_ the issue is detected. [ci-all] --------- Co-authored-by: Robin Malfait <malfait.robin@gmail.com>
2025-05-09 14:55:02 +02:00
"index.d.ts",
"scripts/install.js"
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",
Download platform specific package if `optionalDependencies` are skipped (#17929) Closes #15806 This PR adds a new `postinstall` script to `@tailwindcss/oxide` that will attempt to download the platform-specific optional dependency to avoid issues when the package manager does not do that automatically (see #15806). The implementation for this is fairly simple: The npm package is downloaded from the official npm servers and extracted into the `node_modules` directory of the `@tailwidncss/oxide` installation. ## Test plan Since we still lack a solid repro of #15806, the way I tested this change was to manually remove all automatically-installed optional dependencies and then running the postinstall script manually. The script then downloads the right version package which makes the import to `@tailwidncss/oxide` work. An appropriate integration test was added too. I furthermore also validated that: - This works across CI platforms [ci-all] - The postinstall script bails out when running `pnpm install` in the dev setup. This is necessary since doing the initial install won't have any binary dependencies yet so it would download invalid versions from npm (as the version numbers locally refer to the last released version). We can safely bail out here though since this was never an issue with local development. - The postinstall script does not do anything when the `@tailwindcss/oxide` library is added _unless_ the issue is detected. [ci-all] --------- Co-authored-by: Robin Malfait <malfait.robin@gmail.com>
2025-05-09 14:55:02 +02:00
"version": "napi version",
"postinstall": "node ./scripts/install.js"
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