Skip to content

build(deps): bump @tailwindcss/vite from 4.1.6 to 4.3.0 - #3

Closed
dependabot[bot] wants to merge 1 commit into
masterfrom
dependabot/npm_and_yarn/tailwindcss/vite-4.3.0
Closed

build(deps): bump @tailwindcss/vite from 4.1.6 to 4.3.0#3
dependabot[bot] wants to merge 1 commit into
masterfrom
dependabot/npm_and_yarn/tailwindcss/vite-4.3.0

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github May 13, 2026 •
edited
Loading

Copy link
Copy Markdown

Bumps @tailwindcss/vite from 4.1.6 to 4.3.0.

Release notes

Sourced from @​tailwindcss/vite's releases.

v4.3.0

Added

  • Add @container-size utility (#18901)
  • Add scrollbar-{auto,thin,none} utilities for scrollbar-width, and scrollbar-thumb-* / scrollbar-track-* color utilities for scrollbar-color (#19981, #20019)
  • Add scrollbar-gutter-* utilities (#20018)
  • Add zoom-* utilities (#20020)
  • Add tab-* utilities (#20022)
  • Allow using @variant with stacked variants (e.g. @variant hover:focus { … }) (#19996)
  • Allow using @variant with compound variants (e.g. @variant hover, focus { … }) (#19996)
  • Support --default(…) in --value(…) and --modifier(…) for functional @utility definitions (#19989)

Fixed

  • Ensure @plugin resolves package JavaScript entries instead of browser CSS entries when using @tailwindcss/vite (#19949)
  • Fix relative @import and @plugin paths resolving from the wrong directory when using @tailwindcss/vite (#19965)
  • Ensure CSS files containing @variant are processed by @tailwindcss/vite (#19966)
  • Resolve imports relative to base when result.opts.from is not provided when using @tailwindcss/postcss (#19980)
  • Canonicalization: preserve significant _ whitespace in arbitrary values (#19986)
  • Canonicalization: add parentheses when removing whitespace from arbitrary values would hurt readability (e.g. w-[calc(100%---spacing(60))] → w-[calc(100%-(--spacing(60)))]) (#19986)
  • Canonicalization: preserve the original unit in arbitrary values instead of normalizing to base units (e.g. -mt-[20in] → mt-[-20in], not mt-[-1920px]) (#19988)
  • Canonicalization: migrate arbitrary :has() variants from [&:has(…)] to has-[…] (#19991)
  • Upgrade: don’t migrate inline style attributes (e.g. style="flex-grow: 1" → style="flex-grow: 1", not style="grow: 1") (#19918)
  • Allow multiple @utility definitions with the same name but different value types (#19777)
  • Export missing PluginWithConfig type from tailwindcss/plugin to fix errors when inferring plugin config types (#19707)
  • Ensure start and end legacy utilities without values do not generate CSS (#20003)
  • Ensure --value(…) is required in functional @utility definitions (#20005)
  • Canonicalization: preserve required whitespace around operators in negated arbitrary values (e.g. -left-[(var(--a)+var(--b))]) (#20011)

v4.2.4

Fixed

  • Ensure imports in @import and @plugin still resolve correctly when using Vite aliases in @tailwindcss/vite (#19947)

v4.2.3

Fixed

  • Canonicalization: improve canonicalizations for tracking-* utilities by preferring non-negative utilities (e.g. -tracking-tighter → tracking-wider) (#19827)
  • Fix crash due to invalid characters in candidate (exceeding valid unicode code point range) (#19829)
  • Ensure query params in imports are considered unique resources when using @tailwindcss/webpack (#19723)
  • Canonicalization: collapse arbitrary values into shorthand utilities (e.g. px-[1.2rem] py-[1.2rem] → p-[1.2rem]) (#19837)
  • Canonicalization: collapse border-{t,b}-* into border-y-*, border-{l,r}-* into border-x-*, and border-{t,r,b,l}-* into border-* (#19842)
  • Canonicalization: collapse scroll-m{t,b}-* into scroll-my-*, scroll-m{l,r}-* into scroll-mx-*, and scroll-m{t,r,b,l}-* into scroll-m-* (#19842)
  • Canonicalization: collapse scroll-p{t,b}-* into scroll-py-*, scroll-p{l,r}-* into scroll-px-*, and scroll-p{t,r,b,l}-* into scroll-p-* (#19842)
  • Canonicalization: collapse overflow-{x,y}-* into overflow-* (#19842)
  • Canonicalization: collapse overscroll-{x,y}-* into overscroll-* (#19842)
  • Read from --placeholder-color instead of --background-color for placeholder-* utilities (#19843)
  • Upgrade: ensure files are not emptied out when killing the upgrade process while it's running (#19846)
  • Upgrade: use config.content when migrating from Tailwind CSS v3 to Tailwind CSS v4 (#19846)
  • Upgrade: never migrate files that are ignored by git (#19846)

... (truncated)

Changelog

Sourced from @​tailwindcss/vite's changelog.

[4.3.0] - 2026-05-08

Added

  • Add @container-size utility (#18901)
  • Add scrollbar-{auto,thin,none} utilities for scrollbar-width, and scrollbar-thumb-* / scrollbar-track-* color utilities for scrollbar-color (#19981, #20019)
  • Add scrollbar-gutter-* utilities (#20018)
  • Add zoom-* utilities (#20020)
  • Add tab-* utilities (#20022)
  • Allow using @variant with stacked variants (e.g. @variant hover:focus { … }) (#19996)
  • Allow using @variant with compound variants (e.g. @variant hover, focus { … }) (#19996)
  • Support --default(…) in --value(…) and --modifier(…) for functional @utility definitions (#19989)

Fixed

  • Ensure @plugin resolves package JavaScript entries instead of browser CSS entries when using @tailwindcss/vite (#19949)
  • Fix relative @import and @plugin paths resolving from the wrong directory when using @tailwindcss/vite (#19965)
  • Ensure CSS files containing @variant are processed by @tailwindcss/vite (#19966)
  • Resolve imports relative to base when result.opts.from is not provided when using @tailwindcss/postcss (#19980)
  • Canonicalization: preserve significant _ whitespace in arbitrary values (#19986)
  • Canonicalization: add parentheses when removing whitespace from arbitrary values would hurt readability (e.g. w-[calc(100%---spacing(60))] → w-[calc(100%-(--spacing(60)))]) (#19986)
  • Canonicalization: preserve the original unit in arbitrary values instead of normalizing to base units (e.g. -mt-[20in] → mt-[-20in], not mt-[-1920px]) (#19988)
  • Canonicalization: migrate arbitrary :has() variants from [&:has(…)] to has-[…] (#19991)
  • Upgrade: don’t migrate inline style attributes (e.g. style="flex-grow: 1" → style="flex-grow: 1", not style="grow: 1") (#19918)
  • Allow multiple @utility definitions with the same name but different value types (#19777)
  • Export missing PluginWithConfig type from tailwindcss/plugin to fix errors when inferring plugin config types (#19707)
  • Ensure start and end legacy utilities without values do not generate CSS (#20003)
  • Ensure --value(…) is required in functional @utility definitions (#20005)
  • Canonicalization: preserve required whitespace around operators in negated arbitrary values (e.g. -left-[(var(--a)+var(--b))]) (#20011)

[4.2.4] - 2026-04-21

Fixed

  • Ensure imports in @import and @plugin still resolve correctly when using Vite aliases in @tailwindcss/vite (#19947)

[4.2.3] - 2026-04-20

Fixed

  • Canonicalization: improve canonicalization for tracking-* utilities by preferring non-negative utilities (e.g. -tracking-tighter → tracking-wider) (#19827)
  • Fix crash due to invalid characters in candidate (exceeding valid unicode code point range) (#19829)
  • Ensure query params in imports are considered unique resources when using @tailwindcss/webpack (#19723)
  • Canonicalization: collapse arbitrary values into shorthand utilities (e.g. px-[1.2rem] py-[1.2rem] → p-[1.2rem]) (#19837)
  • Canonicalization: collapse border-{t,b}-* into border-y-*, border-{l,r}-* into border-x-*, and border-{t,r,b,l}-* into border-* (#19842)
  • Canonicalization: collapse scroll-m{t,b}-* into scroll-my-*, scroll-m{l,r}-* into scroll-mx-*, and scroll-m{t,r,b,l}-* into scroll-m-* (#19842)
  • Canonicalization: collapse scroll-p{t,b}-* into scroll-py-*, scroll-p{l,r}-* into scroll-px-*, and scroll-p{t,r,b,l}-* into scroll-p-* (#19842)
  • Canonicalization: collapse overflow-{x,y}-* into overflow-* (#19842)
  • Canonicalization: collapse overscroll-{x,y}-* into overscroll-* (#19842)
  • Read from --placeholder-color instead of --background-color for placeholder-* utilities (#19843)

... (truncated)

Commits
Maintainer changes

This version was pushed to npm by GitHub Actions, a new releaser for @​tailwindcss/vite since your current version.

@dependabot dependabot Bot added dependencies Pull requests that update a dependency file javascript Pull requests that update javascript code labels May 13, 2026
@dependabot
dependabot Bot force-pushed the dependabot/npm_and_yarn/tailwindcss/vite-4.3.0 branch from feb4f6b to c95b712 Compare May 16, 2026 09:47
alsterg added a commit that referenced this pull request May 22, 2026
@alsterg
docs(grep_search): document pattern fallback in parser and renumber gaps
54c2601 
Added Gap #1 describing the parser-level pattern → query fallback
in NativeToolCallParser.ts, explaining why models confabulate
'pattern' (cross-tool name collision with sed/find_files) and
how the fix works without schema pollution. Renumbered existing
gaps #2–#7 to #3–#8.

chore(release): bump version to 0.22.27
@dependabot
build(deps): bump @tailwindcss/vite from 4.1.6 to 4.3.0
635ff5b 
Bumps [@tailwindcss/vite](https://github.com/tailwindlabs/tailwindcss/tree/HEAD/packages/@tailwindcss-vite) from 4.1.6 to 4.3.0.
- [Release notes](https://github.com/tailwindlabs/tailwindcss/releases)
- [Changelog](https://github.com/tailwindlabs/tailwindcss/blob/main/CHANGELOG.md)
- [Commits](https://github.com/tailwindlabs/tailwindcss/commits/v4.3.0/packages/@tailwindcss-vite)

---
updated-dependencies:
- dependency-name: "@tailwindcss/vite"
  dependency-version: 4.3.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot Bot changed the title chore(deps): bump @tailwindcss/vite from 4.1.6 to 4.3.0 build(deps): bump @tailwindcss/vite from 4.1.6 to 4.3.0 May 22, 2026
@dependabot
dependabot Bot force-pushed the dependabot/npm_and_yarn/tailwindcss/vite-4.3.0 branch from c95b712 to 635ff5b Compare May 22, 2026 07:27
alsterg added a commit that referenced this pull request May 25, 2026
@alsterg
fix(shofer): move getFullModeDetails out of shared/ (WelcomeView hotfix
86554ff 
#3)

Hotfixes #1 (08cb900) and #2 (09d3858) purged the static `vscode`
import from `src/shared/experiments.ts` and `src/shared/modes.ts`
respectively. But `src/shared/modes.ts` still re-exported
`getFullModeDetails`, which transitively imported
`addCustomInstructions` from `src/core/prompts/sections/custom-
instructions.ts` — and that module imports `fs/promises`, `path`, and
`os`. The webview bundler cannot resolve Node built-ins any more than
it can resolve `vscode`, so the webview chunk still carried a stale
`shared/modes.ts` source-content reference to a host-only module and
the bundle still crashed at load time with `Uncaught TypeError: Failed
to resolve module specifier "vscode"` — surfaced this time from the
chain modes.ts → custom-instructions.ts.

(The reason the symptom looked identical even though the *direct*
offender had moved: the cached webview build under
`src/webview-ui/build/` was being replayed by turbo because edits to
`src/shared/*` did not invalidate the webview package's per-package
input hash. Fixed in the superproject by f537a95 which wires
`--no-cache` to wipe turbo/vite/tsbuildinfo caches for extension
builds. With that flag in hand a clean rebuild confirmed the bundle no
longer contains `import "vscode"`.)

Fix: move `getFullModeDetails` (the only remaining host-coupled symbol
in `src/shared/modes.ts`) into the new host-only module
`src/core/modes/getFullModeDetails.ts`, alongside its host-only spec
under `src/core/modes/__tests__/getFullModeDetails.test.ts`. Drop the
`addCustomInstructions` import from `src/shared/modes.ts`, and strip
the now-stale `getFullModeDetails` cases out of the webview-side
`src/shared/__tests__/modes.spec.ts`. Update the single host caller in
`src/core/environment/getEnvironmentDetails.ts` to import from the new
location.

Per the "Shared Module Isolation Rule" in AGENTS.md, files under
`src/shared/` MUST NOT statically import host-only modules — that
includes anything reaching `vscode`, `fs/promises`, `path`, `os`, or
host services. This commit closes the last such offender in modes.ts.

Bumps version to 0.26.14.
@alsterg alsterg closed this May 28, 2026
@alsterg
alsterg deleted the dependabot/npm_and_yarn/tailwindcss/vite-4.3.0 branch May 28, 2026 14:43
@dependabot @github

dependabot Bot commented on behalf of github May 28, 2026

Copy link
Copy Markdown
Author

OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting @dependabot ignore this major version or @dependabot ignore this minor version. You can also ignore all major, minor, or patch releases for a dependency by adding an ignore condition with the desired update_types to your config file.

If you change your mind, just re-open this PR and I'll resolve any conflicts on it.

alsterg added a commit that referenced this pull request Jun 10, 2026
@alsterg
fix(smoke-harness): add mock scenario for architect test and SIGINT b…
44fef05 
…ypass

Add a dedicated mock scenario matching the architect mode prompt so test #13
passes on the mock provider. Guard test #21 (SIGINT) behind a real-provider
check — the prompt contains "number" which hits the built-in mock scenario
and returns instantly, so SIGINT always lands after rc=0 on mock.

Closes issues #2 and #3 from todos/fixing_tests.md.
alsterg added a commit that referenced this pull request Jun 13, 2026
@alsterg
docs(model_preferences): mark Shofer Cloud tool-prefs section as NOT …
62b63de 
…WIRED

resolveVersionedSettings (versionedSettings.ts) is unit-tested but has no
production callers, and the Shofer Cloud API that would fetch these
settings doesn't exist in this fork (per cloud.md). Added a NOT-WIRED
banner so readers don't mistake the dormant versioned-settings design for
runtime behavior; the live prefs are the local OpenAI-router/Gemini/Vertex
ones. Resolved the doc's own gap #3.
alsterg added a commit that referenced this pull request Jun 13, 2026
@alsterg
docs(special-files): reconcile stale gaps with current code
f0e8698 
- Gap #2 claimed ShoferIgnoreController is dead code; it is now central
  and widely used (Task.ts every-task instantiation, code indexer,
  assistant agent, tree-sitter, ripgrep, context-management). Marked
  resolved.
- PROTECTED_PATTERNS no longer contains .shoferrules* (it's now
  .shofer/**, .vscode/**, *.code-workspace, .shoferprotected, AGENTS.md,
  AGENT.md). Reconciled the stale .shoferrules* gaps (#3, #4, #6) and added
  the missing .shoferprotected row to the write-protected summary table.
- Fixed a ghost 'rules-ask/' example (no Ask mode) -> rules-code-search/.
alsterg added a commit that referenced this pull request Jun 13, 2026
@alsterg
docs(tool-registration): correct browser-tools 'hypothetical' gap
ba45a6b 
The browser-tools extension does exist now, but it does not implement the
getDefinitions/invokeTool private-tool-provider contract (only showExecutors/
showOutput/showPreview). Corrected gap #3 (which claimed no such extension
exists) and annotated the settings.json example's browser-tools entry as
illustrative (switched the fence to jsonc for the comment). Left the
arkware/shofer namespace-mismatch gap documented — fixing it touches
vscode-tools which has uncommitted changes.
alsterg added a commit that referenced this pull request Jun 15, 2026
@alsterg
docs(drag_n_drop): design for drag & drop into workflow input forms
7d422b2 
Add a 'design only — not yet implemented' section exploring how dragging a
file from the VSCode Explorer could populate the typed input form that
collects workflow params (WorkflowParamForm / FollowUpData.paramForm), which
now also backs mid-flow escalate forms.

Key points: form-control fields receive drop events reliably on Desktop
(same exception ChatTextArea relies on), so per-field onDrop beats the native
TreeView (which can't target a field); a declared 'accepts: path|paths|content'
trait gates which fields are droppable; reuses extractUriPayload/parseDroppedUris;
cwd wiring (Known-issues #3) and shoferignore filtering are prerequisites;
OS-file drags stay unsupported (Electron). Includes a slang-author surface sketch
and open questions. No code changes.
alsterg added a commit that referenced this pull request Jul 7, 2026
@alsterg
fix(webview): make mode-selector rows keyboard/AT operable (a11y)
3463363 
The mode rows were plain onClick divs with no role/tabindex/keyboard handling,
so screen readers couldn't operate the menu and automation had no per-row ref.
Make the list a labelled role=listbox and each row a focusable role=option with
aria-selected, tabIndex=0, an Enter/Space onKeyDown mirroring the click, and a
focus-visible ring. (shofer-ui-known-bugs #3)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

dependencies Pull requests that update a dependency file javascript Pull requests that update javascript code

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

1 participant

@alsterg