chore(deps): update dependency vite-plugin-dynamic-base to ^1.4.1

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
vite-plugin-dynamic-base	^1.3.0 → ^1.4.1

---

Release Notes

chenxch/vite-plugin-dynamic-base (vite-plugin-dynamic-base)

v1.4.1

Compare Source

v1.4.0

Compare Source

2026-05-09

Fix

• fix template literal asset path transformation for Vite 8 so asset URLs in template literals are correctly rewritten to use dynamic publicPath.

---

Configuration

📅 Schedule: (UTC)

• Branch creation
  • At any time (no schedule defined)
• 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.

[xrgzs]

需要合并一下之前patch的修改，1.4.0可能并未完全修复问题

[pikachuren]

结论：请求修改 — 本地 patch 无法应用到新版本

Build Check 失败原因很明确：

[ERR_PNPM_PATCH_FAILED] Could not apply patch
  patches/vite-plugin-dynamic-base.patch
  to node_modules/.pnpm/vite-plugin-dynamic-base@1.4.1_patch_hash=...

仓库在 pnpm-workspace.yaml 里对这个依赖挂了本地补丁：

patchedDependencies:
  # if https://github.com/chenxch/vite-plugin-dynamic-base/pull/36 is merged,
  # this patch can be removed
  vite-plugin-dynamic-base: patches/vite-plugin-dynamic-base.patch

补丁改的是 dist/core/utils.js 里的 replaceInStringLiteral 和 replaceInTemplateElement，1.4.1 的这两个函数实现发生了变化，上下文对不上导致 patch 应用失败，安装阶段直接中断。

这里有个前置判断需要先做：补丁注释指向上游 PR chenxch/vite-plugin-dynamic-base#36，如果 1.4.1 已经合入了等价修复，那么正确做法不是重做补丁，而是连同补丁一起删除——保留一个功能重复的补丁反而可能把已修好的行为改坏。所以建议按顺序确认：

1. 先核对 1.4.1 的 dist/core/utils.js，看这两处修改（用 literal.raw 而非 literal.value 以保留转义、以及模板字面量替换去掉多余的前导 /）是否已包含在上游；
2. 若已包含，从 pnpm-workspace.yaml 移除 patchedDependencies 条目并删掉 patches/vite-plugin-dynamic-base.patch；
3. 若未包含，用 pnpm patch vite-plugin-dynamic-base@1.4.1 基于新版本重新生成补丁。

无论走哪条路，合并前都需要验证子路径部署（非根 base）下资源路径重写仍然正确，这正是该补丁要解决的问题，回归了不容易被常规构建发现。当前状态不能合并。