Skip to content

Restore the smoke script lost in a package.json merge - #51

Merged
joehoyle merged 1 commit into
mainfrom
fix/restore-smoke-script
Sep 14, 2026
Merged

joehoyle merged 1 commit into
mainfrom
fix/restore-smoke-script

Conversation

@joehoyle

@joehoyle joehoyle commented Sep 14, 2026

Copy link
Copy Markdown
Member

Every push to main and every release since 11 Sep fails at the smoke step with npm error Missing script: "smoke". The 1.1.1 release never made it to npm because of this.

PR #45 was branched in July, before the release process existed, and added its own scripts block containing only test. When it merged onto main, which already had scripts.smoke, the result was a package.json with two scripts keys. JSON parsing keeps the last one, so smoke was silently dropped while scripts/smoke.js stayed in the tree. The Tests workflow kept passing because test survived, which hid the problem.

This collapses the duplicate into one block with both test and smoke. Verified locally that npm run smoke renders the full help output and exits 0.

🤖 Generated with Claude Code

This PR was posted by AI on Joe's behalf.

CI and the release workflow both run npm run smoke, but since PR #45
merged npm reports "Missing script: smoke". That PR was branched before
the release process existed and added its own scripts block with only
test. Merging it onto main left package.json with two scripts keys, and
JSON parsing keeps the last one, so smoke silently disappeared while
scripts/smoke.js stayed in the tree.

Collapse to a single scripts block with both entries.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
@joehoyle
joehoyle merged commit 8e60fd4 into main Sep 14, 2026
4 checks passed
@joehoyle
joehoyle deleted the fix/restore-smoke-script branch September 14, 2026 22:16
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.

2 participants