[Snyk] Fix for 1 vulnerabilities

[snyk-io]

Snyk has created this PR to fix 1 vulnerabilities in the pnpm dependencies of this project.

Snyk changed the following file(s):

• packages/build/package.json

⚠️ Warning

Failed to update the pnpm-lock.yaml, please update manually before merging.

Vulnerabilities that will be fixed with an upgrade:

	Issue
	Resources Downloaded over Insecure Protocol SNYK-JS-ESBUILD-17750822

Breaking Change Risk

Notice: This assessment is enhanced by AI.

---

Important

• Check the changes in this PR to ensure they won't cause issues with your project.
• Max score is 1000. Note that the real score may have changed since the PR was raised.
• This PR was automatically created by Snyk using the credentials of a real user.

---

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open fix PRs.

For more information:
🧐 View latest project report
📜 Customise PR templates
🛠 Adjust project settings
📚 Read about Snyk's upgrade logic

---

Learn how to fix vulnerabilities with free interactive lessons:

🦉 Learn about vulnerability in an interactive lesson of Snyk Learn.

---

This change is 

[snyk-io]

This update includes a significant version jump for esbuild and a corresponding update for tsx, which bundles esbuild. The changes introduce potential breaking changes, primarily related to environment support and internal behavior.

esbuild: 0.23.0 → 0.28.1

This is a large minor version upgrade with several noted backward-incompatible changes across the versions.

Key Changes & Potential Breaks:

• macOS Support Dropped: Version 0.24.0 and later drop support for macOS 10.15 (Catalina) because the underlying Go compiler was updated. [2]
• Behavioral Changes: The changelogs for versions 0.23.0 and 0.24.0 explicitly state they contain "deliberately backwards-incompatible changes". For example, v0.23.0 reverted a default behavior related to how packages are handled with platform=node. [2]
• Security Fixes: The latest versions include security fixes, such as preventing directory traversal in the dev server on Windows. [1, 5]

tsx: 4.17.0 → 4.22.0

The primary change in this upgrade is the update of its internal esbuild dependency to version 0.28.x. [6]

Recommendation:

• Verify Your Environment: If your development or build environment uses macOS, confirm you are on version 11 (Big Sur) or later. [2]
• Review esbuild Configuration: Check the official esbuild changelog for any specific API or CLI flag changes that may affect your build scripts. The change in package handling defaults in v0.23.0 is a notable example to be aware of. [2]
• Test Your Build: Given the number of versions spanned, a full test of your build and development server is highly recommended to catch any unexpected behavioral changes.

Source: esbuild CHANGELOG [1], tsx Release Notes [6]

Notice 🤖: This content was augmented using artificial intelligence. AI-generated content may contain errors and should be reviewed for accuracy before use.

[changeset-bot]

⚠️ No Changeset found

Latest commit: a05980d

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[snyk-io]

✅ 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

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

[snyk-io]

✅ 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

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

[kilo-code-bot]

WARNING: pnpm-lock.yaml was not regenerated for this dependency bump

The PR description explicitly notes: "Failed to update the pnpm-lock.yaml, please update manually before merging." The changed-files list confirms pnpm-lock.yaml is not part of this PR. With this repo's CI typically running pnpm install --frozen-lockfile, the install will fail because the lockfile still resolves esbuild to 0.23.x/tsx to 4.17.0, which no longer satisfies the declared ^0.28.1 / 4.22.0 ranges. Run pnpm install to update the lockfile and commit it before merge.

Also note this is a large esbuild jump (0.23.0 → 0.28.1) spanning several minor releases that the changelog marks as containing deliberate backwards-incompatible changes (e.g. node-platform package handling defaults, dropped macOS Catalina support). Because packages/build is a build tool, a full local build/test should be run after the lockfile is updated to confirm nothing breaks.

---

Reply with @kilocode-bot fix it to have Kilo Code address this issue.

[kilo-code-bot]

Code Review Summary

Status: 1 Issue Found | Recommendation: Address before merge

Overview

Severity	Count
CRITICAL	0
WARNING	1
SUGGESTION	0

Issue Details (click to expand)

WARNING

File	Line	Issue
packages/build/package.json	91	pnpm-lock.yaml was not regenerated for the esbuild/tsx bump; CI frozen-lockfile install will fail and resolved versions won't match. Large esbuild 0.23→0.28 jump has documented backwards-incompatible changes that need a build/test verification.

Files Reviewed (1 file)

• packages/build/package.json - 1 issue

Fix these issues in Kilo Cloud

---

_{Reviewed by hy3-20260706:free · Input: 37.2K · Output: 5.7K · Cached: 208.2K}