chore(deps-dev): bump the dev-dependencies group across 1 directory with 12 updates

[dependabot]

Bumps the dev-dependencies group with 11 updates in the / directory:

Package	From	To
@testing-library/jest-dom	6.6.4	6.7.0
@types/mathjs	9.4.1	9.4.2
@types/node	24.2.1	24.3.0
@typescript-eslint/eslint-plugin	8.39.0	8.39.1
@vitejs/plugin-react	4.7.0	5.0.0
@vitejs/plugin-react-swc	3.11.0	4.0.0
eslint	8.57.1	9.33.0
eslint-plugin-react-hooks	4.6.2	5.2.0
tailwindcss	3.4.17	4.1.12
tsx	4.20.3	4.20.4
vite	5.4.19	7.1.2

Updates @testing-library/jest-dom from 6.6.4 to 6.7.0

Release notes

Sourced from @​testing-library/jest-dom's releases.

v6.7.0

6.7.0 (2025-08-13)

Features

• add toBePressed matcher (#203) (#658) (cfdf8ae)

Commits

• e15f789 docs: add kretajak as a contributor for code, and test (#691)
• cfdf8ae feat: add toBePressed matcher (#203) (#658)
• f00d94d chore: add dependebot.yml (#456)
• 476c30b refactor: drop lodash entirely (#676)
• fafd8ca chore: add tests for Node 22 & 24 (#678)
• d9babb1 docs: fix typo (#667)
• f0f31bb docs: adopt the new build-badge URL (#497)
• See full diff in compare view

Updates @types/mathjs from 9.4.1 to 9.4.2

Commits

• See full diff in compare view

Updates @types/node from 24.2.1 to 24.3.0

Commits

• See full diff in compare view

Updates @typescript-eslint/eslint-plugin from 8.39.0 to 8.39.1

Release notes

Sourced from @​typescript-eslint/eslint-plugin's releases.

v8.39.1

8.39.1 (2025-08-11)

🩹 Fixes

• typescript-eslint: handle file:// urls in stack trace when inferring tsconfigRootDir (#11464)

❤️ Thank You

• Kirk Waiblinger @​kirkwaiblinger

You can read about our versioning strategy and releases on our website.

Changelog

Sourced from @​typescript-eslint/eslint-plugin's changelog.

8.39.1 (2025-08-11)

This was a version bump only for eslint-plugin to align it with other projects, there were no code changes.

You can read about our versioning strategy and releases on our website.

Commits

• b2ee794 chore(release): publish 8.39.1
• fee2bc6 chore: update eslint-plugin-eslint-plugin (#11449)
• See full diff in compare view

Updates @typescript-eslint/parser from 8.39.0 to 8.39.1

Release notes

Sourced from @​typescript-eslint/parser's releases.

v8.39.1

8.39.1 (2025-08-11)

🩹 Fixes

• typescript-eslint: handle file:// urls in stack trace when inferring tsconfigRootDir (#11464)

❤️ Thank You

• Kirk Waiblinger @​kirkwaiblinger

You can read about our versioning strategy and releases on our website.

Changelog

Sourced from @​typescript-eslint/parser's changelog.

8.39.1 (2025-08-11)

This was a version bump only for parser to align it with other projects, there were no code changes.

You can read about our versioning strategy and releases on our website.

Commits

• b2ee794 chore(release): publish 8.39.1
• See full diff in compare view

Updates @vitejs/plugin-react from 4.7.0 to 5.0.0

Release notes

Sourced from @​vitejs/plugin-react's releases.

[email protected]

(Same content as v5.0.0-beta.0 https://github.com/vitejs/vite-plugin-react/releases/tag/plugin-react%405.0.0-beta.0)

Use Oxc for react refresh transform in rolldown-vite

When used with rolldown-vite, this plugin now uses Oxc for react refresh transform.

Since this behavior is what @vitejs/plugin-react-oxc did, @vitejs/plugin-react-oxc is now deprecated and the disableOxcRecommendation option is removed.

Also, while @vitejs/plugin-react-oxc used the production JSX transform even for NODE_ENV=development build, @vitejs/plugin-react uses the development JSX transform for NODE_ENV=development build.

Allow processing files in node_modules

The default value of exclude options is now [/\/node_modules\//] to allow processing files in node_modules directory. It was previously [] and files in node_modules was always excluded regardless of the value of exclude option.

react and react-dom is no longer added to resolve.dedupe automatically

Adding values to resolve.dedupe forces Vite to resolve them differently from how Node.js does, which can be confusing and may not be expected. This plugin no longer adds react and react-dom to resolve.dedupe automatically.

If you encounter errors after upgrading, check your package.json for version mismatches in dependencies or devDependencies, as well as your package manager’s configuration. If you prefer the previous behavior, you can manually add react and react-dom to resolve.dedupe.

Remove old babel-plugin-react-compiler support that requires runtimeModule option

runtimeModule option is no longer needed in newer babel-plugin-react-compiler versions. Make sure to use a newer version of babel-plugin-react-compiler that supports target option.

Require Node 20.19+, 22.12+

This plugin now requires Node 20.19+ or 22.12+.

[email protected]

Use Oxc for react refresh transform in rolldown-vite

When used with rolldown-vite, this plugin now uses Oxc for react refresh transform.

Since this behavior is what @vitejs/plugin-react-oxc did, @vitejs/plugin-react-oxc is now deprecated and the disableOxcRecommendation option is removed.

Also, while @vitejs/plugin-react-oxc used the production JSX transform even for NODE_ENV=development build, @vitejs/plugin-react uses the development JSX transform for NODE_ENV=development build.

Allow processing files in node_modules

The default value of exclude options is now [/\/node_modules\//] to allow processing files in node_modules directory. It was previously [] and files in node_modules was always excluded regardless of the value of exclude option.

react and react-dom is no longer added to resolve.dedupe automatically

Adding values to resolve.dedupe forces Vite to resolve them differently from how Node.js does, which can be confusing and may not be expected. This plugin no longer adds react and react-dom to resolve.dedupe automatically.

If you encounter errors after upgrading, check your package.json for version mismatches in dependencies or devDependencies, as well as your package manager’s configuration. If you prefer the previous behavior, you can manually add react and react-dom to resolve.dedupe.

Remove old babel-plugin-react-compiler support that requires runtimeModule option

... (truncated)

Changelog

Sourced from @​vitejs/plugin-react's changelog.

5.0.0 (2025-08-07)

5.0.0-beta.0 (2025-07-28)

Use Oxc for react refresh transform in rolldown-vite

When used with rolldown-vite, this plugin now uses Oxc for react refresh transform.

Since this behavior is what @vitejs/plugin-react-oxc did, @vitejs/plugin-react-oxc is now deprecated and the disableOxcRecommendation option is removed.

Also, while @vitejs/plugin-react-oxc used the production JSX transform even for NODE_ENV=development build, @vitejs/plugin-react uses the development JSX transform for NODE_ENV=development build.

Allow processing files in node_modules

The default value of exclude options is now [/\/node_modules\//] to allow processing files in node_modules directory. It was previously [] and files in node_modules was always excluded regardless of the value of exclude option.

react and react-dom is no longer added to resolve.dedupe automatically

Adding values to resolve.dedupe forces Vite to resolve them differently from how Node.js does, which can be confusing and may not be expected. This plugin no longer adds react and react-dom to resolve.dedupe automatically.

If you encounter errors after upgrading, check your package.json for version mismatches in dependencies or devDependencies, as well as your package manager’s configuration. If you prefer the previous behavior, you can manually add react and react-dom to resolve.dedupe.

Remove old babel-plugin-react-compiler support that requires runtimeModule option

runtimeModule option is no longer needed in newer babel-plugin-react-compiler versions. Make sure to use a newer version of babel-plugin-react-compiler that supports target option.

Require Node 20.19+, 22.12+

This plugin now requires Node 20.19+ or 22.12+.

Commits

• 9e4a944 release: [email protected]
• 61d777d fix(deps): update all non-major dependencies (#670)
• 7d3a57a release: [email protected]
• 9ffd86d fix(react): use development jsx transform for NODE_ENV=development build (#...
• 133d786 feat: merge plugin-react-oxc into plugin-react (#609)
• 26326b3 feat!: support including files in node_modules (#306)
• 9ce3b22 fix(deps): update all non-major dependencies (#593)
• cadd7d2 fix!: remove resolve.dedupe (#586)
• 005f16e refactor!: remove old babel-plugin-react-compiler support (#584)
• b9efa3f refactor!: bump required node version to 20.19+, 22.12+ and drop CJS build (#...
• Additional commits viewable in compare view

Updates @vitejs/plugin-react-swc from 3.11.0 to 4.0.0

Release notes

Sourced from @​vitejs/plugin-react-swc's releases.

[email protected]

Options changes

include/exclude

These options now allow to completely override the files processed by the plugin (#122). This is more in line with other Rollup/Vite plugins and simplify the setup of enabling Fast Refresh for .mdx files. This can be done like this:

export default defineConfig({
  plugins: [
    { enforce: 'pre', ...mdx() },
    react({ include: /\.(mdx|js|jsx|ts|tsx)$/ }),
  ],
})

These changes also allow to apply Babel plugins on files outside Vite root (expect in node_modules), which improve support for monorepo (fix #16).

With these changes, only the file extensions is used for filtering processed files and the query param fallback is removed.

jsxRuntime

The support for React auto import when using classic runtime is removed. This was prone to errors and added complexity for no good reason given the very wide support of automatic runtime nowadays. This migration path should be as simple as removing the runtime option from the config.

Removed options

• fastRefresh (#122) This should be correctly activated by plugin without configuration.
• jsxPure (#129) This is a niche use case that was just passing down the boolean to esbuild.jsxSideEffects.

Perf

This release goes in hand with the upcoming Vite 4.3 release focusing on performances:

• Cache plugin load (#141)
• Wrap dynamic import to speedup analysis (#143)

Other notable changes

• Silence "use client" warning (#144, fix #137)
• Fast Refresh is applied on JS files using automatic runtime (#122, fix #83)
• Vite 4.2 is required as a peer dependency (#128)
• Avoid key collision in React refresh registration (a74dfef, fix #116)
• Throw when refresh runtime is loaded twice (#108, fix #101)
• Don't force optimization of jsx-runtime (#132)

[email protected]

(Same content as v4.0.0-beta.0 https://github.com/vitejs/vite-plugin-react/releases/edit/plugin-react-swc%404.0.0-beta.0)

Require Node 20.19+, 22.12+

... (truncated)

Changelog

Sourced from @​vitejs/plugin-react-swc's changelog.

4.0.0 (2025-08-07)

4.0.0-beta.0 (2025-07-28)

Require Node 20.19+, 22.12+

This plugin now requires Node 20.19+ or 22.12+.

Commits

• See full diff in compare view

Updates eslint from 8.57.1 to 9.33.0

Release notes

Sourced from eslint's releases.

v9.33.0

Features

• e07820e feat: add global object access detection to no-restricted-globals (#19939) (sethamus)
• 90b050e feat: support explicit resource management in one-var (#19941) (Sweta Tanwar)

Bug Fixes

• 732433c fix: allow any type for meta.docs.recommended in custom rules (#19995) (Francesco Trotta)
• e8a6914 fix: Fixed potential bug in check-emfile-handling.js (#19975) (諏訪原慶斗)

Documentation

• 34f0723 docs: playground button for TypeScript code example (#19671) (Tanuj Kanti)
• dc942a4 docs: Update README (GitHub Actions Bot)
• 5a4b6f7 docs: Update no-multi-assign.md (#19979) (Yuki Takada (Yukinosuke Takada))
• 247e156 docs: add missing let declarations in no-plusplus (#19980) (Yuki Takada (Yukinosuke Takada))
• 0d17242 docs: Update README (GitHub Actions Bot)
• fa20b9d docs: Clarify when to open an issue for a PR (#19974) (Nicholas C. Zakas)

Build Related

• 27fa865 build: use ESLint class to generate formatter examples (#19972) (Milos Djermanovic)

Chores

• 4258046 chore: update dependency @​eslint/js to v9.33.0 (#19998) (renovate[bot])
• ad28371 chore: package.json update for @​eslint/js release (Jenkins)
• 06a22f1 test: resolve flakiness in --mcp flag test (#19993) (Pixel998)
• 54920ed test: switch to Linter.Config in ESLintRules type tests (#19977) (Francesco Trotta)

v9.32.0

Features

• 1245000 feat: support explicit resource management in core rules (#19828) (fnx)
• 0e957a7 feat: support typescript types in accessor rules (#19882) (fnx)

Bug Fixes

• 960fd40 fix: Upgrade @​eslint/js (#19971) (Nicholas C. Zakas)
• bbf23fa fix: Refactor reporting into FileReport (#19877) (Nicholas C. Zakas)
• d498887 fix: bump @​eslint/plugin-kit to 0.3.4 to resolve vulnerability (#19965) (Milos Djermanovic)
• f46fc6c fix: report only global references in no-implied-eval (#19932) (Nitin Kumar)
• 7863d26 fix: remove outdated types in ParserOptions.ecmaFeatures (#19944) (ntnyq)
• 3173305 fix: update execScript message in no-implied-eval rule (#19937) (TKDev7)

Documentation

• 86e7426 docs: Update README (GitHub Actions Bot)

Chores

• 50de1ce chore: package.json update for @​eslint/js release (Jenkins)
• 74f01a3 ci: unpin jiti to version ^2.5.1 (#19970) (루밀LuMir)
• 2ab1381 ci: pin jiti to version 2.4.2 (#19964) (Francesco Trotta)
• b7f7545 test: switch to flat config mode in SourceCode tests (#19953) (Milos Djermanovic)
• f5a35e3 test: switch to flat config mode in eslint-fuzzer (#19960) (Milos Djermanovic)
• e22af8c refactor: use CustomRuleDefinitionType in JSRuleDefinition (#19949) (Francesco Trotta)
• e855717 chore: switch performance tests to hyperfine (#19919) (Francesco Trotta)

... (truncated)

Changelog

Sourced from eslint's changelog.

v9.33.0 - August 8, 2025

• 4258046 chore: update dependency @​eslint/js to v9.33.0 (#19998) (renovate[bot])
• ad28371 chore: package.json update for @​eslint/js release (Jenkins)
• 06a22f1 test: resolve flakiness in --mcp flag test (#19993) (Pixel998)
• 732433c fix: allow any type for meta.docs.recommended in custom rules (#19995) (Francesco Trotta)
• 34f0723 docs: playground button for TypeScript code example (#19671) (Tanuj Kanti)
• dc942a4 docs: Update README (GitHub Actions Bot)
• 5a4b6f7 docs: Update no-multi-assign.md (#19979) (Yuki Takada (Yukinosuke Takada))
• 247e156 docs: add missing let declarations in no-plusplus (#19980) (Yuki Takada (Yukinosuke Takada))
• 0d17242 docs: Update README (GitHub Actions Bot)
• e07820e feat: add global object access detection to no-restricted-globals (#19939) (sethamus)
• fa20b9d docs: Clarify when to open an issue for a PR (#19974) (Nicholas C. Zakas)
• 54920ed test: switch to Linter.Config in ESLintRules type tests (#19977) (Francesco Trotta)
• e8a6914 fix: Fixed potential bug in check-emfile-handling.js (#19975) (諏訪原慶斗)
• 90b050e feat: support explicit resource management in one-var (#19941) (Sweta Tanwar)
• 27fa865 build: use ESLint class to generate formatter examples (#19972) (Milos Djermanovic)

v9.32.0 - July 25, 2025

• 960fd40 fix: Upgrade @​eslint/js (#19971) (Nicholas C. Zakas)
• 50de1ce chore: package.json update for @​eslint/js release (Jenkins)
• bbf23fa fix: Refactor reporting into FileReport (#19877) (Nicholas C. Zakas)
• 74f01a3 ci: unpin jiti to version ^2.5.1 (#19970) (루밀LuMir)
• d498887 fix: bump @​eslint/plugin-kit to 0.3.4 to resolve vulnerability (#19965) (Milos Djermanovic)
• 2ab1381 ci: pin jiti to version 2.4.2 (#19964) (Francesco Trotta)
• b7f7545 test: switch to flat config mode in SourceCode tests (#19953) (Milos Djermanovic)
• f5a35e3 test: switch to flat config mode in eslint-fuzzer (#19960) (Milos Djermanovic)
• f46fc6c fix: report only global references in no-implied-eval (#19932) (Nitin Kumar)
• 86e7426 docs: Update README (GitHub Actions Bot)
• e22af8c refactor: use CustomRuleDefinitionType in JSRuleDefinition (#19949) (Francesco Trotta)
• 1245000 feat: support explicit resource management in core rules (#19828) (fnx)
• e855717 chore: switch performance tests to hyperfine (#19919) (Francesco Trotta)
• 0e957a7 feat: support typescript types in accessor rules (#19882) (fnx)
• 2f73a23 test: switch to flat config mode in ast-utils tests (#19948) (Milos Djermanovic)
• 7863d26 fix: remove outdated types in ParserOptions.ecmaFeatures (#19944) (ntnyq)
• c565a53 chore: exclude further_reading_links.json from Prettier formatting (#19943) (Milos Djermanovic)
• 3173305 fix: update execScript message in no-implied-eval rule (#19937) (TKDev7)

v9.31.0 - July 11, 2025

• 3ddd454 chore: upgrade to @eslint/[email protected] (#19935) (Francesco Trotta)
• d5054e5 chore: package.json update for @​eslint/js release (Jenkins)
• 0f4a378 chore: update eslint (#19933) (renovate[bot])
• 664cb44 docs: Update README (GitHub Actions Bot)
• 07fac6c fix: retry on EMFILE when writing autofix results (#19926) (TKDev7)
• 35cf44c feat: output full actual location in rule tester if different (#19904) (ST-DDT)
• 40dbe2a docs: fix mismatch between globalIgnores() code and text (#19914) (MaoShizhong)
• 76c2340 chore: bump mocha to v11 (#19917) (루밀LuMir)
• 28cc7ab fix: Remove incorrect RuleContext types (#19910) (Nicholas C. Zakas)

... (truncated)

Commits

• a90d7c4 9.33.0
• 9534b55 Build: changelog update for 9.33.0
• 4258046 chore: update dependency @​eslint/js to v9.33.0 (#19998)
• ad28371 chore: package.json update for @​eslint/js release
• 06a22f1 test: resolve flakiness in --mcp flag test (#19993)
• 732433c fix: allow any type for meta.docs.recommended in custom rules (#19995)
• 34f0723 docs: playground button for TypeScript code example (#19671)
• dc942a4 docs: Update README
• 5a4b6f7 docs: Update no-multi-assign.md (#19979)
• 247e156 docs: add missing let declarations in no-plusplus (#19980)
• Additional commits viewable in compare view

Updates eslint-plugin-react-hooks from 4.6.2 to 5.2.0

Release notes

Sourced from eslint-plugin-react-hooks's releases.

[email protected] (Oct 11, 2024)

This release only contains eslint-plugin-react-hooks. Notably, new violations and support for ESLint v9 were added.

eslint-plugin-react-hooks

• New Violations: Component names now need to start with an uppercase letter instead of a non-lowercase letter. This means _Button or _component are no longer valid. (@​kassens) in #25162 For example, in

  function _Component() {
    useState()
    ^^^^^^^^ A React Hook "useState" is called in function "_Component" which is neither a Component nor a custom React Hook function.
  }

  _Component should be renamed to Component.

• Add support for ESLint v9. (@​eps1lon in #28773)
• Consider dispatch from useActionState stable. (@​eps1lon in #29665)
• Accept as expression in callback. (@​StyleShit in #28202)
• Accept as expressions in deps array. (@​StyleShit in #28189)
• Treat React.use() the same as use(). (@​kassens in #27769)
• Move use() lint to non-experimental. (@​kassens in #27768)
• Support Flow as expressions. (@​cpojer in #27590)
• Allow useEffect(fn, undefined). (@​kassens in #27525)
• Disallow hooks in async functions. (@​acdlite in #27045)
• Rename experimental useEvent to useEffectEvent. (@​sebmarkbage in #25881)
• Lint for presence of useEvent functions in dependency lists. (@​poteto in #25512)
• Check useEvent references instead. (@​poteto in #25319)
• Update RulesOfHooks with useEvent rules. (@​poteto in #25285)

Changelog

Sourced from eslint-plugin-react-hooks's changelog.

5.2.0

• Support flat config (@​michaelfaith in #30774)
• Convert the plugin to TypeScript and provide package type declarations (@​michaelfaith in #32279, #32283, #32240, #32400 and @​poteto in #32420)
• Fix false positive error in components with do/while loops (@​tyxla in #31720)
• Detect issues in class properties (@​mjesun & @​ecraig12345 in #31823)

5.1.0

• Add support for do/while loops (@​tyxla in #28714)
• Fix error when callback argument is an identifier with an as expression (@​mskelton in #31119)

5.0.0

• New Violations: Component names now need to start with an uppercase letter instead of a non-lowercase letter. This means _Button or _component are no longer valid. (@​kassens) in #25162

• Consider dispatch from useActionState stable. (@​eps1lon in #29665)
• Add support for ESLint v9. (@​eps1lon in #28773)
• Accept as expression in callback. (@​StyleShit in #28202)
• Accept as expressions in deps array. (@​StyleShit in #28189)
• Treat React.use() the same as use(). (@​kassens in #27769)
• Move use() lint to non-experimental. (@​kassens in #27768)
• Support Flow as expressions. (@​cpojer in #27590)
• Allow useEffect(fn, undefined). (@​kassens in #27525)
• Disallow hooks in async functions. (@​acdlite in #27045)
• Rename experimental useEvent to useEffectEvent. (@​sebmarkbage in #25881)
• Lint for presence of useEvent functions in dependency lists. (@​poteto in #25512)
• Check useEvent references instead. (@​poteto in #25319)
• Update RulesOfHooks with useEvent rules. (@​poteto in #25285)

4.6.0

4.5.0

• Fix false positive error with large number of branches. (@​scyron6 in #24287)

4.4.0

• No changes, this was an automated release together with React 18.

4.3.0

• Support ESLint 8. (@​MichaelDeBoey in #22248)
• Fix a crash with an empty effect. (@​ChrisRu in #20385)
• Improve the error message. (@​callmetwan in #20692)
• Handle optional chained methods as dependency. (@​AriPerkkio in #20247)
• Assume the new useTransition signature in the rule. (@​rickhanlonii in #20976)

4.2.0

... (truncated)

Commits

• See full diff in compare view

Updates tailwindcss from 3.4.17 to 4.1.12

Release notes

Sourced from tailwindcss's releases.

v4.1.12

Fixed

• Don't consider the global important state in @apply (#18404)
• Add missing suggestions for flex-<number> utilities (#18642)
• Fix trailing ) from interfering with extraction in Clojure keywords (#18345)
• Detect classes inside Elixir charlist, word list, and string sigils (#18432)
• Track source locations through @plugin and @config (#18345)
• Allow boolean values of process.env.DEBUG in @tailwindcss/node (#18485)
• Ignore consecutive semicolons in the CSS parser (#18532)
• Center the dropdown icon added to an input with a paired datalist by default (#18511)
• Extract candidates in Slang templates (#18565)
• Improve error messages when encountering invalid functional utility names (#18568)
• Discard CSS AST objects with false or undefined properties (#18571)
• Allow users to disable URL rebasing in @tailwindcss/postcss via transformAssetUrls: false (#18321)
• Fix false-positive migrations in addEventListener and JavaScript variable names (#18718)
• Fix Standalone CLI showing default Bun help when run via symlink on Windows (#18723)
• Read from --border-color-* theme keys in divide-* utilities for backwards compatibility (#18704)
• Don't scan .hdr and .exr files for classes by default (#18734)

v4.1.11

Fixed

• Add heuristic to skip candidate migrations inside emit(…) (#18330)
• Extract candidates with variants in Clojure/ClojureScript keywords (#18338)
• Document --watch=always in the CLI's usage (#18337)
• Add support for Vite 7 to @tailwindcss/vite (#18384)

v4.1.10

Fixed

• Fix incorrectly generated CSS when using percentages in arbitrary values with calc (e.g. w-[calc(100%-var(--offset))]) (#18289)

v4.1.9

Fixed

• Correctly parse custom properties with strings containing semicolons (#18251)
• Upgrade: Migrate arbitrary modifiers without percentage signs to bare values (e.g. /[0.16] → /16) (#18184)
• Upgrade: Migrate CSS variable shorthands where fallback value contains function call (#18184)
• Upgrade: Migrate negative arbitrary values to negative bare values (e.g. mb-[-32rem] → -mb-128) (#18212)
• Upgrade: Do not migrate blur in wire:model.blur (#18216)
• Don't add spaces around CSS dashed idents when formatting math expressions (#18220)

v4.1.8

Added

• Improve error messages when @apply fails (#18059)

Fixed

... (truncated)

Changelog

Sourced from tailwindcss's changelog.

[4.1.12] - 2025-08-13

Fixed

• Don't consider the global important state in @apply (#18404)
• Add missing suggestions for flex-<number> utilities (#18642)
• Fix trailing ) from interfering with extraction in Clojure keywords (#18345)
• Detect classes inside Elixir charlist, word list, and string sigils (#18432)
• Track source locations through @plugin and @config (#18345)
• Allow boolean values of process.env.DEBUG in @tailwindcss/node (#18485)
• Ignore consecutive semicolons in the CSS parser (#18532)
• Center the dropdown icon added to an input with a paired datalist by default (#18511)
• Extract candidates in Slang templates (#18565)
• Improve error messages when encountering invalid functional utility names (#18568)
• Discard CSS AST objects with false or undefined properties (#18571)
• Allow users to disable URL rebasing in @tailwindcss/postcss via transformAssetUrls: false (#18321)
• Fix false-positive migrations in addEventListener and JavaScript variable names (#18718)
• Fix Standalone CLI showing default Bun help when run via symlink on Windows (#18723)
• Read from --border-color-* theme keys in divide-* utilities for backwards compatibility (#18704)
• Don't scan .hdr and .exr files for classes by default (#18734)

[4.1.11] - 2025-06-26

Fixed

• Add heuristic to skip candidate migrations inside emit(…) (#18330)
• Extract candidates with variants in Clojure/ClojureScript keywords (#18338)
• Document --watch=always in the CLI's usage (

[netlify]

❌ Deploy Preview for gridfinity-drawer-planner failed.

Name	Link
🔨 Latest commit	e774799
🔍 Latest deploy log	https://app.netlify.com/projects/gridfinity-drawer-planner/deploys/68ac0742e07f650008df4c7b

[github-actions]

PR Quality Report 📊

Check	Status
TypeScript	✅
ESLint	✅
Tests	✅
Build	✅

View detailed results

[ntindle]

@dependabot recreate

[claude]

Claude finished @dependabot[bot]'s task —— View job

---

Code Review Complete ✅

Comprehensive analysis of the Dependabot PR updating 12 dev dependencies. Here's my detailed review:

Review Checklist:

• Read project context from CLAUDE.md
• Analyze package.json changes
• Check for breaking changes in major version updates
• Review configuration compatibility
• Run tests and build verification
• Provide comprehensive feedback

---

🔍 Analysis Summary

This PR updates 12 development dependencies with several major version bumps that require careful attention:

Package	From	To	Risk Level
ESLint	8.57.1	9.33.0	⚠️ HIGH
Vite	5.4.19	7.1.2	⚠️ HIGH
Tailwind CSS	3.4.17	4.1.12	⚠️ HIGH
@vitejs/plugin-react	4.7.0	5.0.0	⚠️ MEDIUM
@vitejs/plugin-react-swc	3.11.0	4.0.0	⚠️ MEDIUM
eslint-plugin-react-hooks	4.6.2	5.2.0	✅ LOW
Others (type definitions, etc.)	Various	Various	✅ LOW

---

🚨 Critical Breaking Changes

1. ESLint 8 → 9 (BREAKING)

• Flat config is now required - your existing eslint.config.js is already compatible ✅
• New rules and behavior changes - some rules may behave differently
• Plugin compatibility - all your plugins support ESLint 9 ✅

2. Vite 5 → 7 (BREAKING)

• Node.js requirement: Now requires Node 18+ (you appear to be compatible)
• Plugin API changes: Some plugins may need updates
• Build behavior changes: New optimizations and bundling strategies
• Your config looks compatible but testing is required ✅

3. Tailwind CSS 3 → 4 (BREAKING)

• Complete rewrite with new engine and syntax
• Breaking changes to utilities and configuration
• Your config may need updates for v4 compatibility
• This is the highest risk change ⚠️

---

🛡️ Security Assessment

✅ POSITIVE: All updates include security fixes and vulnerability patches

• ESLint 9: Fixes several security vulnerabilities
• Vite 7: Includes security improvements and dependency updates
• No known security regressions in any updated packages

---

🔧 Configuration Compatibility

ESLint Configuration ✅

Your eslint.config.js is already using flat config format, which is required for ESLint 9.

Vite Configuration ⚠️

Your vite.config.js uses:

• @vitejs/plugin-react-swc - updated to v4 (should be compatible)
• Custom build configuration - may need adjustment for Vite 7

Tailwind Configuration ⚠️

Your tailwind.config.js uses v3 syntax which may not be fully compatible with v4.

---

🧪 Recommended Testing Strategy

1. Install dependencies: npm install
2. Test build: npm run build
3. Test dev server: npm run dev
4. Run linting: npm run lint
5. Run tests: npm test
6. Check Tailwind styles - manually verify no visual regressions

---

⚠️ High-Risk Areas to Monitor

1. Tailwind CSS Styles: The v3→v4 upgrade could break existing utility classes
2. Build Pipeline: Vite 7 changes may affect bundling and chunk splitting
3. Hot Module Replacement: Dev server behavior may change with Vite 7
4. ESLint Rules: New rules may flag previously acceptable code

---

🔧 Potential Required Actions

If Tailwind v4 breaks compatibility:

# Rollback Tailwind to v3.x
npm install tailwindcss@^3.4.17 --save-dev

If Vite 7 causes issues:

• Check vite.config.js for deprecated options
• Update build.rollupOptions if needed
• Verify plugin compatibility

ESLint Rule Updates:

• May need to add rule exceptions if new rules are too strict
• Check for new recommended rules to adopt

---

📊 Performance Considerations

✅ POSITIVE IMPACT:

• Vite 7: Improved build speeds and tree-shaking
• ESLint 9: Better performance for large codebases
• React plugins: Better Fast Refresh performance

⚠️ MONITOR:

• Bundle size changes due to Vite 7 optimizations
• Build time changes
• Dev server startup time

---

🎯 Recommendation

🚨 PROCEED WITH CAUTION: This PR contains significant breaking changes, particularly Tailwind CSS v3→v4.

Suggested approach:

1. ✅ Merge and test thoroughly in a staging environment
2. ⚠️ Be prepared to rollback Tailwind CSS if styles break
3. 🧪 Test all UI components for visual regressions
4. 🔧 Update configurations as needed based on test results

Critical success factors:

• All tests must pass
• No visual regressions in the UI
• Dev and build processes work correctly
• No new ESLint errors introduced

The project's comprehensive test suite (187 tests) and TypeScript coverage should help catch most compatibility issues early.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
⚠️ Please upload report for BASE (main@5633261). Learn more about missing BASE report.

Additional details and impacted files

@@           Coverage Diff           @@
##             main      #25   +/-   ##
=======================================
  Coverage        ?   64.43%           
=======================================
  Files           ?       49           
  Lines           ?     3430           
  Branches        ?      319           
=======================================
  Hits            ?     2210           
  Misses          ?     1198           
  Partials        ?       22           

Flag	Coverage Δ
unittests	64.43% <ø> (?)

Flags with carried forward coverage won't be shown. Click here to find out more.

🚀 New features to boost your workflow:

• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[ntindle]

@claude format this

[claude]

Claude finished @ntindle's task —— View job

---

📦 Dependency Update Review

⚡ Quick Summary

12 dev dependencies with 3 major breaking changes that require attention.

🚨 Critical Breaking Changes

Package	Version Jump	Impact
ESLint	8.57.1 → 9.33.0	Flat config required (✅ already compatible)
Vite	5.4.19 → 7.1.2	Node 18+ required, plugin API changes
Tailwind CSS	3.4.17 → 4.1.12	⚠️ Complete rewrite - highest risk

✅ Action Items

1. Test thoroughly before merging:

   npm install
   npm run build
   npm run dev
   npm run lint
   npm test

2. Watch for issues in:

   • Tailwind utility classes (v3→v4 breaking changes)
   • Build output and bundle sizes
   • Dev server behavior
   • Any new ESLint errors

3. If problems occur:

   • Tailwind: Consider rolling back to v3 (npm install tailwindcss@^3.4.17 --save-dev)
   • Document any config changes needed for v4 compatibility

📋 Full Dependency List

Package	From	To	Type
@testing-library/jest-dom	6.6.4	6.7.0	patch
@types/mathjs	9.4.1	9.4.2	patch
@types/node	24.2.1	24.3.0	minor
@typescript-eslint/eslint-plugin	8.39.0	8.39.1	patch
@typescript-eslint/parser	8.39.0	8.39.1	patch
@vitejs/plugin-react	4.7.0	5.0.0	major
@vitejs/plugin-react-swc	3.11.0	4.0.0	major
eslint	8.57.1	9.33.0	major
eslint-plugin-react-hooks	4.6.2	5.2.0	major
tailwindcss	3.4.17	4.1.12	major
tsx	4.20.3	4.20.4	patch
vite	5.4.19	7.1.2	major

🔍 Detailed Breaking Change Analysis

ESLint 8 → 9

• ✅ Your flat config is compatible
• New rules may flag previously valid code
• All plugins support v9

Vite 5 → 7

• Requires Node.js 18+ minimum
• New build optimizations
• Plugin API changes (your plugins should be compatible)
• Monitor bundle size and build times

Tailwind CSS 3 → 4

• Highest risk change - complete engine rewrite
• Many utility classes changed or removed
• Configuration syntax updates required
• Visual regression testing essential

React Plugin Updates

• @vitejs/plugin-react v5: No longer adds react/react-dom to resolve.dedupe
• @vitejs/plugin-react-swc v4: Requires Node 20.19+ or 22.12+
• eslint-plugin-react-hooks v5: Component names must start with uppercase

🎯 Recommendation

Merge with caution - The Tailwind v3→v4 upgrade is the highest risk. Your comprehensive test suite (187 tests) should catch most issues, but manual UI testing is essential for Tailwind changes.

---