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:

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](698d9c4bd1)
to decompile the binary first.
---------
Co-authored-by: Jordan Pittman <jordan@cryptica.me>
Co-authored-by: Robin Malfait <malfait.robin@gmail.com>
14 KiB
14 KiB
Changelog
All notable changes to this project will be documented in this file.
The format is based on Keep a Changelog, and this project adheres to Semantic Versioning.
[Unreleased]
Added
- Add new standalone builds of Tailwind CSS v4 (#14270)
Fixed
- Bring back type exports for the cjs build of
@tailwindcss/postcss(#14256) - Correctly merge tuple values when using the plugin API (#14260)
- Handle arrays in the CSS
theme()function when using plugins (#14262) - Fix fallback values when using the CSS
theme()function (#14262) - Fix support for declaration fallbacks in plugins (#14265)
- Support bare values when using
tailwindcss/defaultTheme(#14257)
[4.0.0-alpha.20] - 2024-08-23
Added
- Add support for
addBaseplugins using the@plugindirective (#14172) - Add support for the
tailwindcss/pluginexport (#14173) - Add support for the
theme()function in plugins (#14207) - Add support for
addComponents,matchComponents,prefixplugin APIs (#14221) - Add support for
tailwindcss/colorsandtailwindcss/defaultThemeexports for use with plugins (#14221) - Add support for the
@tailwindcss/typographyand@tailwindcss/formsplugins (#14221) - Add support for the
theme()function in CSS and class names (#14177) - Add support for matching multiple utility definitions for one candidate (#14231)
Fixed
- Don't wrap relative selectors in arbitrary variants with
:is(…)(#14203)
[4.0.0-alpha.19] - 2024-08-09
Added
- Add support for
inlineoption when defining@themevalues (#14095) - Add
inertvariant (#14129) - Add support for explicitly registering content paths using new
@sourceat-rule (#14078) - Add support for scanning
<style>tags in Vue files to the Vite plugin (#14158) - Add support for basic
addUtilitiesandmatchUtilitiesplugins using the@plugindirective (#14114)
Fixed
- Ensure
@applyworks inside@utility(#14144)
[4.0.0-alpha.18] - 2024-07-25
Added
- Add support for basic
addVariantplugins with new@plugindirective (#13982, #14008) - Add
@variantat-rule for defining custom variants in CSS (#13992, #14008) - Add
@utilityat-rule for defining custom utilities in CSS (#14044)
Fixed
- Discard invalid classes such as
bg-red-[#000](#13970) - Fix parsing body-less at-rule without terminating semicolon (#13978)
- Ensure opacity modifier with variables work with
color-mix()(#13972) - Discard invalid
variantsandutilitieswith modifiers (#13977) - Add missing utilities that exist in v3, such as
resize,fill-none,accent-none,drop-shadow-none, and negativehue-rotateandbackdrop-hue-rotateutilities (#13971) - Don’t allow at-rule-only variants to be compounded (#14015)
- Ensure compound variants work with variants with multiple selectors (#14016)
- Ensure attribute values in
data-*andaria-*modifiers are always quoted in the generated CSS (#14040)
Changed
- Reduce the specificity of the
*variant so those styles can be overridden by child elements (#14056)
[4.0.0-alpha.17] - 2024-07-04
Added
- Add
rounded-4xlutility (#13827) - Add
backdrop-blur-noneandblur-noneutilities (#13831) - Include variable in output for bare utilities like
rounded(#13836)
Fixed
- Support combining arbitrary shadows without a color with shadow color utilities (#13876)
- Ensure
@propertyfallbacks work correctly with properties with noinitial-value(#13949)
[4.0.0-alpha.16] - 2024-06-07
Added
- Add
nth-*variants (#13661) - Add
bg-linear-*utilities as an alias for the existingbg-gradient-*utilities (#13783) - Support arbitrary linear gradient angles (e.g.
bg-linear-[125deg]) (#13783)
Fixed
- Use
lengthdata type forbackground-sizeinstead ofbackground-position(#13771) - Support negative values for
{col,row}-{start,end}utilities (#13780) - Use long form
<length> | <percentage>syntax for properties (#13660) - Fix background position value of
bg-right-top,bg-right-bottom,bg-left-bottomandbg-left-top(#13806)
[4.0.0-alpha.15] - 2024-05-08
Fixed
- Make sure
contain-*utility variables resolve to a valid value (#13521) - Support unbalanced parentheses and braces in quotes in arbitrary values and variants (#13608)
- Add fallbacks for
@propertyrules for Firefox (#13655)
Changed
- Use
remunits for breakpoints by default instead ofpx(#13469) - Use natural sorting when sorting classes (#13507, #13532)
[4.0.0-alpha.14] - 2024-04-09
Fixed
- Ensure deterministic SSR builds in
@tailwindcss/vite(#13457)
Changed
- Apply variants from left to right instead of inside-out (#13478)
- Don't special-case
[hidden]elements inspace-*/divide-*utilities (#13459)
[4.0.0-alpha.13] - 2024-04-04
Fixed
- Always inline values for
shadow-*utilities to ensure shadow colors work correctly (#13449)
[4.0.0-alpha.12] - 2024-04-04
Fixed
- Enable Vite's
waitForRequestsIdle()for client requests only (#13394) - Make sure
::first-letterrespects::selectionstyles (#13408)
[4.0.0-alpha.11] - 2024-03-27
Added
- Make
rotate-x/y/z-*utilities composable (#13319) - Apply Vite's CSS plugin transform to Tailwind-generated CSS in
@tailwindcss/vite(e.g. inlining images) (#13218) - Add
startingvariant for@starting-style(#13329) - Target
:popover-openin existingopenvariant (#13331)
Fixed
- Remove percentage values for
translate-zutilities (#13321, #13327) - Generate unique CSS bundle hashes in
@tailwindcss/vitewhen Tailwind-generated CSS changes (#13218) - Inherit letter spacing in form controls (#13328)
- Ensure
buildcommand is executed when using--outputinstead of-o(#13369) - Prevent
@tailwindcss/vitefrom hanging in serve mode (#13380)
[4.0.0-alpha.10] - 2024-03-19
Added
Fixed
- Validate bare values (#13245)
- Parse candidates in
.sveltefiles withclass:abc="condition"syntax (#13274)
Changed
- Inline
@importrules intailwindcss/index.cssat publish time for better performance (#13233) - Include custom properties with fallbacks in utility class values (#13177)
[4.0.0-alpha.9] - 2024-03-13
Added
- Support
@theme reference { … }for defining theme values without emitting variables (#13222)
Fixed
- Fix incorrect properties in line-clamp utilities (#13220)
- Don't rely on existence of
--default-transition-*variables intransition-*utilities (#13219)
Changed
- Move
optimizeCssto the packages where it's used (#13230)
[4.0.0-alpha.8] - 2024-03-11
Fixed
- Ensure
scale-*utilities support percentage values (#13182) - Prevent
content-nonefrom being overridden when conditionally styling::before/::after(#13187) - Remove default borders from
iframeelements (#13189)
Changed
- Replace
--radius-noneand--radius-fulltheme values with staticrounded-noneandrounded-fullutilities (#13186)
Added
- Improve performance of incremental rebuilds for
@tailwindcss/cli(#13169) - Improve performance of incremental rebuilds for
@tailwindcss/postcss(#13170)
[4.0.0-alpha.7] - 2024-03-08
Added
- Add
font-stretchutilities (#13153) - Publish packages with npm provenance (#13160)
- Build native packages for Android (#13115, #13161)
- Make CSS optimization and minification configurable in PostCSS plugin and CLI (#13130)
Fixed
- Don't error on
@applywith leading/trailing whitespace (#13144) - Correctly parse CSS using Windows line endings (#13162)
[4.0.0-alpha.6] - 2024-03-07
Fixed
- Only set
border-stylefor appropriate border side (#13124)
Changed
- Error when
@themecontains unsupported rules/declarations (#13125)
[4.0.0-alpha.5] - 2024-03-06
Fixed
- Don't scan ignored files even if a
.gitfolder is not present (#13119)
[4.0.0-alpha.4] - 2024-03-06
Fixed
- Support importing framework CSS files without including a
.cssextension (#13110)
[4.0.0-alpha.3] - 2024-03-06
Added
- Support putting the important modifier at the beginning of a utility (#13103)
Fixed
- Node compatibility fix (#13104)
Changes
- Drop deprecated
decoration-sliceanddecoration-cloneutilities (#13107)
[4.0.0-alpha.2] - 2024-03-06
Changed
- Move the CLI into a separate
@tailwindcss/clipackage (#13095)