Skip to content

Fix CI: repair broken package.json / pnpm-lock.yaml from unresolved merge conflict - #123

Open
prodbycorne wants to merge 1 commit into
mainfrom
fix/ci-broken-lockfile-package-json
Open

Fix CI: repair broken package.json / pnpm-lock.yaml from unresolved merge conflict#123
prodbycorne wants to merge 1 commit into
mainfrom
fix/ci-broken-lockfile-package-json

Conversation

@prodbycorne

Copy link
Copy Markdown
Contributor

Summary

Both CI workflows (`E2E Tests`, `Deploy to GitHub Pages`) have been failing on every run on `main` since PR #58 merged. Root cause: that merge left both sides of a conflict concatenated instead of resolved.

  • `package.json`: a duplicate `"playwright"` script entry with a missing comma before it — invalid JSON, so `npm ci` fails immediately with `EJSONPARSE`.
  • `pnpm-lock.yaml`: duplicate `version:` mapping keys under `@vitest/coverage-v8` and `vitest` — invalid YAML, so `pnpm install --frozen-lockfile` fails with `ERR_PNPM_BROKEN_LOCKFILE`.

Fix

  • Removed the duplicate `"playwright"` script line from `package.json`.
  • Regenerated `pnpm-lock.yaml` from scratch using pnpm 9 (matching the version CI's `pnpm/action-setup` installs) so it resolves cleanly against the corrected `package.json`.

Test plan

  • `npm ci` — succeeds (was failing with `EJSONPARSE`)
  • `BASE_PATH=/smartdrop-frontend NEXT_EXPORT=true npm run build` — succeeds, matching the exact `Deploy to GitHub Pages` steps
  • `pnpm install --frozen-lockfile` — succeeds (was failing with `ERR_PNPM_BROKEN_LOCKFILE`), matching the exact `E2E Tests` install step
  • Playwright E2E run itself — couldn't run locally (Playwright doesn't support Chromium on this machine's macOS version), will confirm via the GitHub Actions run on this PR (Ubuntu runner)

…ck.yaml

A prior merge left both sides of a conflict concatenated instead of
resolved: package.json had a duplicate "playwright" script key with a
missing comma before it (invalid JSON, breaking `npm ci` on every job with
EJSONPARSE), and pnpm-lock.yaml had duplicate "version:" mapping keys under
@vitest/coverage-v8 and vitest (invalid YAML, breaking `pnpm install
--frozen-lockfile` with ERR_PNPM_BROKEN_LOCKFILE).

Removed the duplicate script entry and regenerated the lockfile with pnpm 9
(matching CI's pnpm/action-setup version) so it resolves cleanly against the
now-valid package.json.

Verified locally: `npm ci` + `npm run build` (Deploy to GitHub Pages'
exact steps) succeed, and `pnpm install --frozen-lockfile` (E2E Tests' exact
step) now passes instead of failing on the broken lockfile.
@netlify

netlify Bot commented Jul 28, 2026

Copy link
Copy Markdown

Deploy Preview for spiffy-melomakarona-eb1e8a ready!

Name Link
🔨 Latest commit b1a64e3
🔍 Latest deploy log https://app.netlify.com/projects/spiffy-melomakarona-eb1e8a/deploys/6a690182f6660800084ad99b
😎 Deploy Preview https://deploy-preview-123--spiffy-melomakarona-eb1e8a.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify project configuration.

@netlify

netlify Bot commented Jul 28, 2026

Copy link
Copy Markdown

Deploy Preview for smart-drop ready!

Name Link
🔨 Latest commit b1a64e3
🔍 Latest deploy log https://app.netlify.com/projects/smart-drop/deploys/6a69018204394c0009207765
😎 Deploy Preview https://deploy-preview-123--smart-drop.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify project configuration.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant