build(deps): bump the npm_and_yarn group across 1 directory with 2 updates

[dependabot]

Bumps the npm_and_yarn group with 2 updates in the / directory: esbuild and vite.

Updates esbuild from 0.21.5 to 0.25.8

Release notes

Sourced from esbuild's releases.

v0.25.8

• Fix another TypeScript parsing edge case (#4248)

  This fixes a regression with a change in the previous release that tries to more accurately parse TypeScript arrow functions inside the ?: operator. The regression specifically involves parsing an arrow function containing a #private identifier inside the middle of a ?: ternary operator inside a class body. This was fixed by propagating private identifier state into the parser clone used to speculatively parse the arrow function body. Here is an example of some affected code:

  class CachedDict {
    #has = (a: string) => dict.has(a);
    has = window
      ? (word: string): boolean => this.#has(word)
      : this.#has;
  }

• Fix a regression with the parsing of source phase imports

  The change in the previous release to parse source phase imports failed to properly handle the following cases:

  import source from 'bar'
  import source from from 'bar'
  import source type foo from 'bar'

  Parsing for these cases should now be fixed. The first case was incorrectly treated as a syntax error because esbuild was expecting the second case. And the last case was previously allowed but is now forbidden. TypeScript hasn't added this feature yet so it remains to be seen whether the last case will be allowed, but it's safer to disallow it for now. At least Babel doesn't allow the last case when parsing TypeScript, and Babel was involved with the source phase import specification.

v0.25.7

• Parse and print JavaScript imports with an explicit phase (#4238)

  This release adds basic syntax support for the defer and source import phases in JavaScript:

  • defer

    This is a stage 3 proposal for an upcoming JavaScript feature that will provide one way to eagerly load but lazily initialize imported modules. The imported module is automatically initialized on first use. Support for this syntax will also be part of the upcoming release of TypeScript 5.9. The syntax looks like this:

    import defer * as foo from "<specifier>";
    const bar = await import.defer("<specifier>");

    Note that this feature deliberately cannot be used with the syntax import defer foo from "<specifier>" or import defer { foo } from "<specifier>".

  • source

    This is a stage 3 proposal for an upcoming JavaScript feature that will provide another way to eagerly load but lazily initialize imported modules. The imported module is returned in an uninitialized state. Support for this syntax may or may not be a part of TypeScript 5.9 (see this issue for details). The syntax looks like this:

    import source foo from "<specifier>";
    const bar = await import.source("<specifier>");

... (truncated)

Changelog

Sourced from esbuild's changelog.

Changelog: 2024

This changelog documents all esbuild versions published in the year 2024 (versions 0.19.12 through 0.24.2).

0.24.2

• Fix regression with --define and import.meta (#4010, #4012, #4013)

  The previous change in version 0.24.1 to use a more expression-like parser for define values to allow quoted property names introduced a regression that removed the ability to use --define:import.meta=.... Even though import is normally a keyword that can't be used as an identifier, ES modules special-case the import.meta expression to behave like an identifier anyway. This change fixes the regression.

  This fix was contributed by @​sapphi-red.

0.24.1

• Allow es2024 as a target in tsconfig.json (#4004)

  TypeScript recently added es2024 as a compilation target, so esbuild now supports this in the target field of tsconfig.json files, such as in the following configuration file:

  {
    "compilerOptions": {
      "target": "ES2024"
    }
  }

  As a reminder, the only thing that esbuild uses this field for is determining whether or not to use legacy TypeScript behavior for class fields. You can read more in the documentation.

  This fix was contributed by @​billyjanitsch.

• Allow automatic semicolon insertion after get/set

  This change fixes a grammar bug in the parser that incorrectly treated the following code as a syntax error:

  class Foo {
    get
    *x() {}
    set
    *y() {}
  }

  The above code will be considered valid starting with this release. This change to esbuild follows a similar change to TypeScript which will allow this syntax starting with TypeScript 5.7.

• Allow quoted property names in --define and --pure (#4008)

  The define and pure API options now accept identifier expressions containing quoted property names. Previously all identifiers in the identifier expression had to be bare identifiers. This change now makes --define and --pure consistent with --global-name, which already supported quoted property names. For example, the following is now possible:

... (truncated)

Commits

• 8c71947 publish 0.25.8 to npm
• 0508f24 some parsing fixes for source phase imports
• 6e4be2f js parser: recover from bad #private identifiers
• c9c6357 fix #4248: #private ids in arrow fn body in ?:
• 9b42f68 publish 0.25.7 to npm
• 9ba01d1 abs-paths: js api and tests
• ca196c9 fix for parser backtracking crash
• 2979b84 fix #4241: ts arrow function type backtrack (hack)
• 1180410 fix an unused variable warning
• fc3da57 fix #4238: add defer and source import phases
• Additional commits viewable in compare view

Updates vite from 5.4.19 to 7.1.1

Release notes

Sourced from vite's releases.

v7.1.1

Please refer to CHANGELOG.md for details.

plugin-legacy@7.1.0

Please refer to CHANGELOG.md for details.

create-vite@7.1.0

Please refer to CHANGELOG.md for details.

v7.1.0

Please refer to CHANGELOG.md for details.

v7.1.0-beta.1

Please refer to CHANGELOG.md for details.

v7.1.0-beta.0

Please refer to CHANGELOG.md for details.

v7.0.6

Please refer to CHANGELOG.md for details.

v7.0.5

Please refer to CHANGELOG.md for details.

v7.0.4

Please refer to CHANGELOG.md for details.

v7.0.3

Please refer to CHANGELOG.md for details.

create-vite@7.0.3

Please refer to CHANGELOG.md for details.

v7.0.2

Please refer to CHANGELOG.md for details.

create-vite@7.0.2

Please refer to CHANGELOG.md for details.

v7.0.1

Please refer to CHANGELOG.md for details.

create-vite@7.0.1

Please refer to CHANGELOG.md for details.

plugin-legacy@7.0.1

Please refer to CHANGELOG.md for details.

create-vite@7.0.0

Please refer to CHANGELOG.md for details.

... (truncated)

Changelog

Sourced from vite's changelog.

7.1.1 (2025-08-08)

Bug Fixes

• deps: update launch-editor-middleware (#20569) (826b394)

Miscellaneous Chores

• fix changelog beta links (#20561) (2e0c21a)
• update 7.1 changelog (#20560) (d8869b8)

7.1.0 (2025-08-07)

Features

• support files with more than 1000 lines by generateCodeFrame (#20508) (e7d0b2a)
• add import.meta.main support in config (bundle config loader) (#20516) (5d3e3c2)
• optimizer: improve dependency optimization error messages with esbuild formatMessages (#20525) (d17cfed)
• ssr: add import.meta.main support for Node.js module runner (#20517) (794a8f2)
• add future: 'warn' (#20473) (e6aaf17)
• add removeServerPluginContainer future deprecation (#20437) (c1279e7)
• add removeServerReloadModule future deprecation (#20436) (6970d17)
• add server.warmupRequest to future deprecation (#20431) (8ad388a)
• add ssrFixStacktrace / ssrRewriteStacktrace to removeSsrLoadModule future deprecation (#20435) (8c8f587)
• client: ping from SharedWorker (#19057) (5c97c22)
• dev: add this.fs support (#20301) (0fe3f2f)
• export defaultExternalConditions (#20279) (344d302)
• implement removePluginHookSsrArgument future deprecation (#20433) (95927d9)
• implement removeServerHot future deprecation (#20434) (259f45d)
• resolve server URLs before calling other listeners (#19981) (45f6443)
• ssr: resolve externalized packages with resolve.externalConditions and add module-sync to default external condition (#20409) (c669c52)
• ssr: support import.meta.resolve in module runner (#20260) (62835f7)

Bug Fixes

• css: avoid warnings for image-set containing __VITE_ASSET__ (#20520) (f1a2635)
• css: empty CSS entry points should generate CSS files, not JS files (#20518) (bac9f3e)
• dev: denied request stalled when requested concurrently (#20503) (64a52e7)
• manifest: initialize entryCssAssetFileNames as an empty Set (#20542) (6a46cda)
• skip prepareOutDirPlugin in workers (#20556) (97d5111)
• asset: only watch existing files for new URL(, import.meta.url) (#20507) (1b211fd)
• client: keep ping on WS constructor error (#20512) (3676da5)
• deps: update all non-major dependencies (#20537) (fc9a9d3)
• don't resolve as relative for specifiers starting with a dot (#20528) (c5a10ec)
• html: allow control character in input stream (#20483) (c12a4a7)
• merge old and new noExternal: true correctly (#20502) (9ebe4a5)
• deps: update all non-major dependencies (#20489) (f6aa04a)
• dev: denied requests overly (#20410) (4be5270)
• hmr: register css deps as type: asset (#20391) (7eac8dd)
• optimizer: discover correct jsx runtime during scan (#20495) (10d48bb)
• preview: set correct host for resolvedUrls (#20496) (62b3e0d)
• worker: resolve WebKit compat with inline workers by deferring blob URL revocation (#20460) (8033e5b)

... (truncated)

Commits

• f4438a1 release: v7.1.1
• 826b394 fix(deps): update launch-editor-middleware (#20569)
• 2e0c21a chore: fix changelog beta links (#20561)
• d8869b8 chore: update 7.1 changelog (#20560)
• 931684e release: v7.1.0
• 97d5111 fix: skip prepareOutDirPlugin in workers (#20556)
• 1f23554 test: fix unimportant errors in test-unit (#20545)
• 856d3f0 test: detect ts support via process.features (#20544)
• f1a2635 fix(css): avoid warnings for image-set containing __VITE_ASSET__ (#20520)
• 6a46cda fix(manifest): initialize entryCssAssetFileNames as an empty Set (#20542)
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
• @dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
• @dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
• @dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
• @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions
  You can disable automated security fix PRs for this repo from the Security Alerts page.

[netlify]

✅ Deploy Preview for gridfinity-drawer-planner ready!

Name	Link
🔨 Latest commit	98b4029
🔍 Latest deploy log	https://app.netlify.com/projects/gridfinity-drawer-planner/deploys/68a7fd7d786af50008a6ecbf
😎 Deploy Preview	https://deploy-preview-7--gridfinity-drawer-planner.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify project configuration.

[ntindle]

@dependabot rebase

[dependabot]

The dependabot.yml entry that created this PR has been deleted so this PR can't be rebased. Please close the PR so Dependabot can create a new one with the current dependabot.yml.

[dependabot]

This pull request was built based on a group rule. Closing it will not ignore any of these versions in future pull requests.

To ignore these dependencies, configure ignore rules in dependabot.yml

[ntindle]

@dependabot recreate

[dependabot]

Looks like this PR is closed. If you re-open it I'll rebase it as long as no-one else has edited it (you can use @dependabot reopen if the branch has been deleted).

[ntindle]

@dependabot reopen

[github-actions]

PR Quality Report 📊

Check	Status
TypeScript	✅
ESLint	✅
Tests	✅
Build	✅

View detailed results

[claude]

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

---

Dependency Update Review ✅

Reviewing this Dependabot PR that updates esbuild (0.21.5 → 0.25.8) and Vite (5.4.19 → 7.1.1).

Review Summary: APPROVE WITH MINOR RECOMMENDATIONS

✅ Code Quality & Compatibility

Vite 7.1.1 Upgrade Analysis:

• ✅ Configuration Compatible: Current vite.config.js uses standard patterns that remain supported
• ✅ No Breaking Changes Detected: Server config, plugins (@vitejs/plugin-react-swc), and build options are all compatible
• ✅ TypeScript Integration: Standard Vite TypeScript setup continues to work
• ✅ CSS/Asset Handling: Basic CSS imports and asset processing unchanged

esbuild 0.25.8 Upgrade Analysis:

• ✅ JavaScript Parsing Improvements: Enhanced support for modern syntax (defer/source imports, es2024)
• ✅ TypeScript Compatibility: Better TypeScript parsing, especially for arrow functions and private fields
• ✅ No Breaking Changes: All improvements are additive, no removal of existing functionality

🔍 Security Assessment

Positive Security Implications:

• ✅ Vulnerability Fixes: Both packages include important security patches
• ✅ Build Security: Newer esbuild has improved handling of malformed inputs
• ✅ Dependency Chain: Updated dependencies reduce potential attack surface

Current CSP Configuration:

• ⚠️ Note: The Content-Security-Policy in vite.config.js:11 includes 'unsafe-eval' which may warrant review but is unrelated to this upgrade

⚡ Performance Considerations

Expected Improvements:

• ✅ Faster Builds: esbuild 0.25.x includes performance optimizations
• ✅ Better Tree Shaking: Vite 7.x has improved dead code elimination
• ✅ Smaller Bundles: Enhanced chunk splitting and optimization

Build Configuration Analysis:

• ✅ Manual Chunks: Well-configured vendor splitting (react-vendor, ui-vendor, math-vendor)
• ✅ Minification: Terser configuration with appropriate optimization settings

🧪 Test Coverage

Test Compatibility:

• ✅ Vitest Integration: No breaking changes for vitest usage patterns
• ✅ TypeScript Tests: All .test.ts files use standard vitest imports that remain supported
• ✅ 187 Tests: Large test suite provides good regression detection

📋 Specific Findings

1. No Deprecated APIs Used: Codebase doesn't use any APIs removed in these versions
2. Standard Plugin Usage: Uses @vitejs/plugin-react-swc which is fully compatible
3. Clean Import Patterns: No problematic import.meta usage or dynamic imports that might break
4. Proper TypeScript Setup: ES2020 target remains appropriate

🚨 Potential Risks

Low Risk Items:

• Major Version Jump: Vite 5.x → 7.x is significant but well-tested transition path
• esbuild Parser Changes: Improved parsing might surface previously hidden syntax issues (unlikely given test coverage)

📝 Recommendations

1. ✅ Approve and Merge: This upgrade is safe and beneficial
2. 🔄 Post-Merge Testing: Run npm run build and npm test after merge to confirm
3. 📊 Performance Monitoring: Monitor build times for expected improvements
4. 🔍 Future CSP Review: Consider reviewing the 'unsafe-eval' CSP directive (separate from this PR)

🎯 Overall Assessment

This dependency update is well-tested, safe, and beneficial. Both tools have excellent backward compatibility records, and the codebase follows standard patterns that remain fully supported. The upgrade brings security fixes, performance improvements, and better developer experience without introducing breaking changes.

Recommendation: ✅ APPROVE

---

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
⚠️ Please upload report for BASE (main@e6a9fa1). Learn more about missing BASE report.
⚠️ Report is 3 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##             main       #7   +/-   ##
=======================================
  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.