No prepack/prepublishOnly build guard: a manual npm publish ships stale/missing dist/
Maintainers usually reply within 1 day
A pull request for this has already been merged.
- #406 by @Kuldeep2822k — merged
Assessment
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Newbie friendliness
- 20/100
- Issue type
- Bug
- Clarity
- Clearly specified
- Activity status
- Stale
- Tech stack
- nodejs, typescript
- Domain
- build-system, release
Research direction
The problem sits in package.json around lines 21-35, where main, types, bin and the build-copied dist/package.json are defined, and no prepack or prepublishOnly script exists. Read the scripts block and check what the build step produces in dist/. Done means a manual npm publish or npm pack rebuilds dist/ first. Pull request #406 already targets this, so review or extend that work rather than starting a new change.
Written by the indexing model from the issue text.
Description
Location: package.json:21-35
Publishing depends entirely on dist/ (main/types/bin + the build-copied dist/package.json imported at runtime). With no prepare/prepack/prepublishOnly, 'npm publish' from a clean or stale checkout ships a tarball with absent/outdated compiled output; a missing dist/package.json crashes the CLI on --version. (CI is safe; manual publish is not.)
Fix: Add "prepack": "npm run build" (or prepublishOnly).
From the 2026-10-10 codebase audit sweep (CODEBASE_AUDIT.md).
- Dominant language
- TypeScript
- Stars
- 1
- Forks
- 0
- Avg merge
- 17h 12m
- Merged PRs (30d)
- 167
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- No contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from Kuldeep2822k/cli
-
bug priority: medium storage
Difficulty 2/5 1-3 hours Newbie friendliness 77/100
Kuldeep2822k/cli#542 ·
Maintainers usually reply within 1 day
-
bug cli priority: medium
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
Kuldeep2822k/cli#541 ·
Maintainers usually reply within 1 day
-
bug priority: medium storage
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Kuldeep2822k/cli#540 ·
Maintainers usually reply within 1 day
-
bug core priority: low
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
Kuldeep2822k/cli#343 · 1 comment ·
Maintainers usually reply within 1 day
-
chore priority: low refactor
Difficulty 5/5 Over a week Newbie friendliness 25/100
Kuldeep2822k/cli#548 ·
Maintainers usually reply within 1 day
All issues in Kuldeep2822k/cli
Similar issues
-
area:cli bug P4
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 1 day
-
bug from-studio
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
esengine/DeepSeek-Reasonix#14868 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
loopbackio/loopback-next#11878 ·
Maintainers usually reply within 2 days
-
bug 🐛
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
comunica/comunica#1925 · 1 comment ·
Maintainers usually reply within 1 day