npm publish decision and execution (H7)
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 10/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Active
- Tech stack
- github-actions, typescript
- Domain
- release
Research direction
Start with the H7 handoff entry in human-tasks.md and confirm whether the usabl name is available on npm. The issue requires a human decision about package name and public source visibility before any publish or CI change; done means recording that decision and, if approved, publishing and updating CI as specified.
Written by the indexing model from the issue text.
Description
Publishing makes the engine public. It is a visibility decision, not an engineering one.
- Why: a public npm package is an irreversible visibility change and should be a deliberate human decision.
- Owner: Founder.
- Prerequisite: confirm the
usablname is available on npm. - Acceptance: a decision is recorded. If yes, the package is published and CI switches from the pinned private checkout to
npm install [email protected]. - Target: v0.2.x.
Status: HELD pending a visibility discussion. Open questions to settle before publishing:
- Name and scope: is the bare name
usablavailable, or do we publish under a scope such as@usabl-dev/usabl? - Visibility: the engine repository is consumed by CI through a private pinned checkout today. Publishing to the public registry exposes the engine source in the package tarball. Confirm that is intended.
- CI switch: after publishing, decide whether and when to move CI from the pinned private checkout to
npm install [email protected], and keep the pin as the trust boundary until then.
Source: human-tasks.md handoff catalogue (H7).
- Dominant language
- TypeScript
- Stars
- 0
- Forks
- 0
- Avg merge
- 2h 48m
- Merged PRs (30d)
- 8
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 usabl-dev/usabl
-
area: engine bug
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
-
Stop hook allows a stop on an unknown verdict, and the self-check prints IDLE for a null verdictOpenarea: assistants bug
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
-
area: engine bug security
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
Overlay: browser context failures are counted per plugin, not per browser, and close is not sharedOpenarea: overlay bug
Difficulty 2/5 1-3 hours Newbie friendliness 64/100
-
area: engine enhancement performance
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
lyswhut/lx-music-desktop#3026 ·
-
area: ci type: test
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
schlessera/brain-kit#2769 ·
Maintainers usually reply within 1 day
-
Read a vector index's quantization back on Neo4j 2026.10, which reports vector.quantization.typeOpen
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
liberation-data/drivine#231 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
alveusgg/alveusgg#2502 · 3 comments ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day