chore(deps-dev): bump vite-plugin-static-copy from 3.1.4 to 4.1.1

[dependabot]

Bumps vite-plugin-static-copy from 3.1.4 to 4.1.1.

Release notes

Sourced from vite-plugin-static-copy's releases.

vite-plugin-static-copy@4.1.1

Patch Changes

• #240 671579b Thanks @​saif-shines! - Use each environment's resolved build.outDir when copying static assets during build. Previously the plugin kept only the last configResolved config, so multi-environment setups (for example Astro with separate client and SSR output directories) could copy files into the wrong folder.

vite-plugin-static-copy@4.1.0

Minor Changes

• #251 7672842 Thanks @​sapphi-red! - Add name property to the rename object form and allow rename functions to return a RenameObject. The name property replaces the file's basename (filename + extension), and can be combined with stripBase to both flatten directory structure and rename the file in one step. Rename functions can now return { name, stripBase } objects instead of only strings, making it easier to declaratively control output paths from dynamic rename logic.

  // node_modules/lib/dist/index.js → vendor/lib.js
  { src: 'node_modules/lib/dist/index.js', dest: 'vendor', rename: { name: 'lib.js', stripBase: true } }
  // src/pages/events/test.html → dist/events/index.html
  { src: 'src/pages/**/*.html', dest: 'dist/', rename: { stripBase: 2, name: 'index.html' } }

vite-plugin-static-copy@4.0.1

Patch Changes

• #249 c6bf44c Thanks @​sapphi-red! - Fix absolute dest paths being nested under the output directory

  When dest was an absolute path and the source file had a directory component (structured output), the path was incorrectly converted to a relative path, causing files to be nested under the build output directory instead of being copied to the specified absolute path.

  { src: 'foo/foo.txt', dest: '/home/user/my-repo/bar' }

  Before: /home/user/my-repo/dist/home/user/my-repo/bar/foo/foo.txt After: /home/user/my-repo/bar/foo/foo.txt

• #247 d3af79e Thanks @​sapphi-red! - Fix rename.stripBase to work correctly with ../ paths

  Previously, stripBase counted .. as directory segments, causing incorrect output paths when copying from parent directories.

  { src: '../../src/pages/**/*.html', dest: 'dist/', rename: { stripBase: 2 } }

  Before: dist/src/pages/events/test.html After: dist/events/test.html

  { src: '../../src/pages/**/*.html', dest: 'dist/', rename: { stripBase: true } }

  Before: dist/src/pages/events/test.html After: dist/test.html

... (truncated)

Changelog

Sourced from vite-plugin-static-copy's changelog.

4.1.1

Patch Changes

• #240 671579b Thanks @​saif-shines! - Use each environment's resolved build.outDir when copying static assets during build. Previously the plugin kept only the last configResolved config, so multi-environment setups (for example Astro with separate client and SSR output directories) could copy files into the wrong folder.

4.1.0

Minor Changes

• #251 7672842 Thanks @​sapphi-red! - Add name property to the rename object form and allow rename functions to return a RenameObject. The name property replaces the file's basename (filename + extension), and can be combined with stripBase to both flatten directory structure and rename the file in one step. Rename functions can now return { name, stripBase } objects instead of only strings, making it easier to declaratively control output paths from dynamic rename logic.

  // node_modules/lib/dist/index.js → vendor/lib.js
  { src: 'node_modules/lib/dist/index.js', dest: 'vendor', rename: { name: 'lib.js', stripBase: true } }
  // src/pages/events/test.html → dist/events/index.html
  { src: 'src/pages/**/*.html', dest: 'dist/', rename: { stripBase: 2, name: 'index.html' } }

4.0.1

Patch Changes

• #249 c6bf44c Thanks @​sapphi-red! - Fix absolute dest paths being nested under the output directory

  When dest was an absolute path and the source file had a directory component (structured output), the path was incorrectly converted to a relative path, causing files to be nested under the build output directory instead of being copied to the specified absolute path.

  { src: 'foo/foo.txt', dest: '/home/user/my-repo/bar' }

  Before: /home/user/my-repo/dist/home/user/my-repo/bar/foo/foo.txt After: /home/user/my-repo/bar/foo/foo.txt

• #247 d3af79e Thanks @​sapphi-red! - Fix rename.stripBase to work correctly with ../ paths

  Previously, stripBase counted .. as directory segments, causing incorrect output paths when copying from parent directories.

  { src: '../../src/pages/**/*.html', dest: 'dist/', rename: { stripBase: 2 } }

  Before: dist/src/pages/events/test.html After: dist/events/test.html

  { src: '../../src/pages/**/*.html', dest: 'dist/', rename: { stripBase: true } }

... (truncated)

Commits

• 63dd788 chore: update versions (#259)
• 671579b fix: use environment-specific outDir in build plugin for Vite 6 (#240)
• 01757de chore(deps): update pnpm to v11
• 707a0fe ci: pin actions
• f0df2ad fix(deps): update all non-major dependencies (#257)
• efb0d50 fix(deps): update all non-major dependencies (#255)
• e95cd6e chore: update versions (#253)
• 7672842 feat: add name property to RenameObject and allow RenameFunc to return ...
• 7ae0134 chore: update versions (#248)
• de515fa chore(deps): update dependency typescript to v6 (#245)
• 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 show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[update-docs]

Thanks for opening this pull request! The maintainers of this repository would appreciate it if you would create a changelog item based on your changes.

[kw-security]

✅ Snyk checks have passed. No issues have been found so far.

Status	Scan Engine	Critical	High	Medium	Low	Total (0)
✅	Open Source Security	0	0	0	0	0 issues
✅	Licenses	0	0	0	0	0 issues
✅	Code Security	0	0	0	0	0 issues

💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[dj4oC]

Bumps vite-plugin-static-copy from 3.1.4 to 4.1.1 (major, root devDependency).

Findings

• Build (blocking, likely unrelated to this diff): Same production-build failure as #13937 and #13939: [vite:worker] ... Transforming destructuring to the configured target environment (...) is not supported yet in packages/web-pkg/src/composables/webWorkers/mfaExpiryWorker/worker.ts, identical file/line across all three unrelated bumps — points to a pre-existing base-branch build break rather than this PR's change.
• Compatibility note: v4 raises the plugin's engines.node requirement to ^22.0.0 || >=24.0.0 (from ^18.0.0 || >=20.0.0) and its vite peer range to ^6.0.0 || ^7.0.0 || ^8.0.0. The repo's pinned vite@7.3.2 still satisfies the new peer range, but worth confirming the CI/build Node version meets the new floor.
• Security: Snyk/CLA passed.
• Performance / Coverage: N/A — build tooling only.

Verdict

Commenting — this PR's own diff looks low-risk, but it can't merge while build is red. See #13937 for the shared root-cause discussion.

🤖 Automated review by Claude Code (security · stability · performance · coverage)

---

Generated by Claude Code