No description
fbf877aa0a
While rebasing on the latest changes on `next`, especially #14160, I noticed that my local `pnpm build` step was no longer working and erring with the following: ``` │ > @tailwindcss/oxide@4.0.0-alpha.19 build /Users/philipp/dev/tailwindcss/crates/node │ > npx napi build --platform --release --no-const-enum │ │ Type Error: Could not parse the Cargo.toml: Error: Command failed: cargo metadata --format-version 1 --manifest-path "/Users/philipp/dev/ │ tailwindcss/crates/node/Cargo.toml" │ error: rustup could not choose a version of cargo to run, because one wasn't specified explicitly, and no default is configured. │ help: run 'rustup default stable' to download the latest stable release of Rust and set it as your default toolchain. │ │ error: rustup could not choose a version of cargo to run, because one wasn't specified explicitly, and no default is configured. │ help: run 'rustup default stable' to download the latest stable release of Rust and set it as your default toolchain. ``` It turns out that with the changes in turbo v2, env variables no longer propagate to the individual tasks automatically but since I installed rustup outside of the default `~/.rustup` directory, the task was no longer able to find it. To fix this, we now define `RUSTUP_HOME` as a global env to always pass through. |
||
|---|---|---|
| .github | ||
| crates | ||
| integrations | ||
| packages | ||
| playgrounds | ||
| scripts | ||
| .gitignore | ||
| .npmrc | ||
| .prettierignore | ||
| Cargo.lock | ||
| Cargo.toml | ||
| CHANGELOG.md | ||
| LICENSE | ||
| package.json | ||
| pnpm-lock.yaml | ||
| pnpm-workspace.yaml | ||
| README.md | ||
| turbo.json | ||
| vitest.workspace.ts | ||
A utility-first CSS framework for rapidly building custom user interfaces.
Documentation
For full documentation, visit tailwindcss.com.
Community
For help, discussion about best practices, or any other conversation that would benefit from being searchable:
Discuss Tailwind CSS on GitHub
For chatting with others using the framework:
Join the Tailwind CSS Discord Server
Contributing
If you're interested in contributing to Tailwind CSS, please read our contributing docs before submitting a pull request.