Bump vendored Tailwind to ^4.3.0 to fix spurious 'Unsupported bare value' warnings for --default()

[benface]

Problem

The Tailwind snapshot vendored into dist/v4-*.mjs is pre-4.3.0, so it lacks the !arg.includes("(") guard that was added in tailwindlabs/tailwindcss#19989 (2026-05-08). Without that guard, --value(...) argument normalization appends a trailing -* to --default(1px), producing --default(1px)-*; the value validator then walks the parsed nodes and warns:

Unsupported bare value data type: "-*".
Only valid data types are: "number", "integer", "ratio", "percentage".

```css
--value([*],--default(1px)-*)
                          ^^

for every `@utility name-*` block whose declarations use `--default(...)`. Real Tailwind 4.3.x parses the same CSS without warnings; the bundled snapshot reproduces it because the guard isn't there.

I hit this via `oxfmt` (which vendors this plugin) on a project defining a functional utility with `--value([*], --default(1px))`, but the root cause is here.

### Reproduce

`utils.css`:

```css
@utility rule-inset-* {
  --mw-rule-inset: --value([*], --default(1px));
}

.prettierrc:

{ "plugins": ["prettier-plugin-tailwindcss"], "tailwindStylesheet": "./entry.css" }

with entry.css importing tailwindcss and utils.css. Then prettier --check (or any host running the sorter) emits N Unsupported bare value warnings.

Fix

Bump tailwindcss-v4: "npm:tailwindcss@^4.1.14" → "^4.3.0" so the rebuild picks up the guarded normalizer. Existing pin allowed 4.3.x semver-wise, but the lockfile stayed on 4.1.18 across insider builds — the specifier bump forces a floor.

Verification

Verified end-to-end:

1. Built this plugin locally with the bump — new dist/v4-*.mjs contains c[0]==="-"&&c[1]==="-"&&!c.includes("(")&&!c.includes("-*")&&(c+="-*") (the guard) instead of the old f[0]==="-"&&f[1]==="-"&&!f.includes("-*")&&(f+="-*").
2. Copied the rebuilt bundle over the vendored one in an oxfmt@0.65.0 install of a monorepo using --default(1px) in three functional utilities. oxfmt --check . went from 24 Unsupported bare value warnings to 0.

Both pnpm build and the existing test suite pass locally after the bump.

Related

• Filed upstream against oxfmt (which vendors this plugin) — oxc-project/oxc#26187 — with the same root-cause analysis.

Edit by @RobinMalfait:
Fixes: #468
Fixes: #471

[snoozbuster]

Likely also fixes #471 (as well as the other issue referenced by that one)

[RobinMalfait]

Thanks!