Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

help: usage text prints a hard-coded program name, not the installed bin name

Closed Beginner friendly
  • Is something wrong?
#314 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

A pull request for this has already been merged.

  • #425 by @Kuldeep2822k — merged

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
66/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Active
Tech stack
nodejs, typescript
Domain
cli

Research direction

The payload names no source files, so start by searching the CLI entry point for the hard-coded palee string and the place where the Commander program is constructed. Run palee --help and a subcommand's --help on a build installed under another bin name to see the usage lines. Done when top-level and subcommand help show the invoked bin name, either by letting program.name() derive it or by passing the derived name through, and the published palee output is unchanged.

Written by the indexing model from the issue text.

Description

documentation priority: low

Summary

Installing the package under a different bin name leaves every help and usage line pointing at palee.

Repro

palee-test --version    # 0.6.0
palee-test --help
  Usage: palee [options] [command]

Subcommand help repeats the same name, so copy-pasting the suggested invocation fails for the renamed binary.

Expected

Commander derives the program name from program.name(), defaulting to the invoked bin. Either let it derive, or make the derived name flow through so renamed and parallel installs stay self-consistent.

Impact

Cosmetic for the published package. It blocks clean dual installs — this audit built palee-test specifically so a worktree build could be exercised without clobbering the published CLI.

Environment
  • palee 0.6.0, local build from main at 02dacd0 (installed as palee-test; reproduce with palee)
  • Node v24.19.0, Windows 11 x64, Git Bash
  • Every command was run for real; exit codes captured by command substitution (never $? after a pipe)
Dominant language
TypeScript
Stars
1
Forks
0
Avg merge
22h 21m
Merged PRs (30d)
167

Getting set up

  • No Dockerfile or Docker Compose file
  • Has a pull request template
  • No contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from Kuldeep2822k/cli

All issues in Kuldeep2822k/cli

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.