chore(deps): update dependency vite-plugin-static-copy to v4

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
vite-plugin-static-copy	^2.3.2 → ^4.0.0

---

Release Notes

sapphi-red/vite-plugin-static-copy (vite-plugin-static-copy)

v4.1.1

Compare Source

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.

v4.1.0

Compare Source

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' } }

v4.0.1

Compare Source

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

v4.0.0

Compare Source

Major Changes

• #​235 b2edc86 Thanks @​sapphi-red! - Simplify glob behavior and always preserve directory structure.

  Breaking changes:

  • Only files are matched. Glob patterns no longer match directory entries. Previously, matching a directory would recursively copy it via fs.cp, which caused files to be copied twice when using ** patterns.
  • Directory patterns are auto-expanded. src: 'assets' now automatically expands to match all files inside the directory, using tinyglobby's built-in expandDirectories option. No migration needed for this pattern alone.
  • structured option removed. Directory structure is now always preserved in the output. The structured option has been removed entirely. Use rename: { stripBase: true } to flatten output paths when needed.

• #​237 6129008 Thanks @​sapphi-red! - Drop support for Vite 5

• #​238 9766e42 Thanks @​sapphi-red! - Drop support for Node 18, 20, 21, 23. The new support range is ^22.0.0 || >= 24.0.0.

v3.4.0

Compare Source

Minor Changes

• #​233 f665a15 Thanks @​sapphi-red! - Add { stripBase: number } object form to the rename option. This strips the given number of leading directory segments from the matched path, avoiding the need for manual ../ traversals in a rename function.

  This is useful when copying files from deep paths like node_modules/my-lib/dist/**/* with structured: true, where the full directory structure would otherwise be preserved in the output. Instead of writing a rename function that manually returns ../ traversals to flatten unwanted nesting, you can use rename: { stripBase: N } to declaratively strip the leading segments.

v3.3.0

Compare Source

Minor Changes

• #​230 3074e1a Thanks @​sapphi-red! - Add Vite 8 to peer dependency range.

v3.2.0

Compare Source

Minor Changes

• #​219 fbb2a7a Thanks @​sapphi-red! - Add environment option to configure which environment the plugin runs in. Defaults to 'client'.

v3.1.6

Compare Source

Patch Changes

• #​217 e3d457d Thanks @​sapphi-red! - Only skip non-client environments when multiple environments exist.

v3.1.5

Compare Source

Patch Changes

• #​214 3f252cc Thanks @​sapphi-red! - Only copy for the client environment.

v3.1.4

Compare Source

Patch Changes

• #​204 d0b5370 Thanks @​stianjensen! - Removed fs-extra dependency in favor of node:fs. This should not affect the behavior.

v3.1.3

Compare Source

Patch Changes

• #​202 9388186 Thanks @​sapphi-red! - Switched to use trusted publisher to publish the package.

v3.1.2

Compare Source

Patch Changes

• #​195 0bc6b49 Thanks @​sapphi-red! - Files not included in src was possible to acess with a crafted request. See GHSA-pp7p-q8fx-2968 for more details.

v3.1.1

Compare Source

Patch Changes

• #​186 fc84156 Thanks @​sapphi-red! - fix a bug that the content was not sent when multiple vite-plugin-static-copy instance was used

v3.1.0

Compare Source

Minor Changes

• #​171 9c7cf2e Thanks @​MrRefactoring! - add Vite 7 to peer dep range

v3.0.2

Compare Source

Patch Changes

• #​167 89458b2 Thanks @​sapphi-red! - improved file grouping algorithm for better performance

v3.0.1

Compare Source

Patch Changes

• #​166 60409c5 Thanks @​sapphi-red! - fix absolute destination paths in copy targets incorrectly returning contents in dev

• #​164 337f976 Thanks @​sapphi-red! - fixes case-insensitive path conflicts causing copy failures (EEXIST error)

v3.0.0

Compare Source

Major Changes

• #​150 71f4f5b Thanks @​sapphi-red! - migrate fast-glob to tinyglobby to reduce the package size and to align with Vite. This breaking change should not affect most users. Check Vite's migration guide for more details.

---

Configuration

📅 Schedule: (in timezone Europe/Oslo)

• Branch creation
  • "before 07:00 on Thursday"
• Automerge
  • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[renovate]

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

• any of the package files in this branch needs updating, or
• the branch becomes conflicted, or
• you click the rebase/retry checkbox if found above, or
• you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: pnpm-lock.yaml

Progress: resolved 1, reused 0, downloaded 0, added 0
 WARN  deprecated @digdir/designsystemet-theme@1.11.0: Use themebuilder at https://theme.designsystemet.no to create your own theme
Progress: resolved 45, reused 0, downloaded 0, added 0
Progress: resolved 189, reused 0, downloaded 0, added 0
 ERR_PNPM_TRUST_DOWNGRADE  High-risk trust downgrade for "semver@6.3.1" (possible package takeover)

This error happened while installing the dependencies of @storybook/react-vite@10.4.1
 at react-docgen@8.0.2
 at @babel/core@7.29.7

Trust checks are based solely on publish date, not semver. A package cannot be installed if any earlier-published version had stronger trust evidence. Earlier versions had provenance attestation, but this version has no trust evidence. A trust downgrade may indicate a supply chain incident.