Files
bitvid/issues/upgrade-esbuild.md
google-labs-jules[bot]andPR0M3TH3AN 8a1d843c24 chore(audit): daily dependency scan and triage
- Generated artifacts/npm-audit.json, artifacts/npm-outdated.json, artifacts/deps-report.md
- Attempted esbuild upgrade (0.27.2 -> 0.27.3) but reverted due to E2E environment failure (see issues/upgrade-esbuild.md)
- Flagged nostr-tools for manual review (see issues/upgrade-nostr-tools.md)
- Updated DECISIONS.md and TODO.md

Co-authored-by: PR0M3TH3AN <[email protected]>
2026-02-12 14:49:04 +00:00

24 lines
835 B
Markdown

# Upgrade Attempt: esbuild (v0.27.2 -> v0.27.3)
**Status:** FAILED (Reverted)
**Date:** 2026-02-17
## Details
Attempted to upgrade `esbuild` from `0.27.2` to `0.27.3`.
## Test Results
- `npm run build`: **PASSED**
- `npm run test:unit`: **PASSED**
- `npm run test:dm:integration`: **PASSED**
- `npm run test:e2e`: **FAILED** (Environment Issue)
## Failure Analysis
The E2E tests failed because the Playwright browser binaries were not found in the CI environment:
```
Error: browserType.launch: Executable doesn't exist at /home/jules/.cache/ms-playwright/chromium_headless_shell-1208/chrome-headless-shell-linux64/chrome-headless-shell
```
## Next Steps
- Ensure the CI/Agent environment has `npx playwright install` run before attempting upgrades that require E2E verification.
- Once browsers are available, retry the upgrade.