chore(deps): update dependency esbuild-plugin-replace to v1.4.0

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
esbuild-plugin-replace (source)	1.0.7 → 1.4.0

---

Release Notes

naecoo/esbuild-plugin-replace (esbuild-plugin-replace)

v1.4.0

Compare Source

v1.3.0

Compare Source

v1.2.1

Compare Source

Update pnpm-lock.yaml and fix one bug.

v1.2.0

Compare Source

• add delimiters option

v1.1.0

Compare Source

add exclude option

v1.0.9

Compare Source

v1.0.8

Compare Source

---

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.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Review	Updated (UTC)
garfish	Ready	Preview, Comment	Jan 8, 2026 5:29pm

[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

(node:1038) [DEP0169] DeprecationWarning: `url.parse()` behavior is not standardized and prone to errors that have security implications. Use the WHATWG URL API instead. CVEs are not issued for `url.parse()` vulnerabilities.
(Use `node --trace-deprecation ...` to show where the warning was created)