Bug: `kdm` Command Not Found After Global Installation

[utkarsh232005]

Summary

After installing kdm-cli globally via npm, the package installs successfully but the kdm command is not available in the terminal.

The installation completes without errors, however executing the CLI results in:

Command 'kdm' not found

---

Steps to Reproduce

1. Install the package globally

npm install -g kdm-cli@latest

2. Run the CLI command

kdm

---

Expected Behavior

The CLI should be accessible globally and execute successfully:

kdm

---

Actual Behavior

Command 'kdm' not found

---

Environment

Component	Version
OS	Ubuntu Linux
Node.js	v24.15.0
npm	11.2.1
Package	kdm-cli@1.2.0

---

Additional Information

The package appears in the global npm package list:

npm list -g --depth=0

Output:

kdm-cli@1.2.0

This indicates the package installs correctly, but no executable binary is being linked globally.

---

Possible Cause

The package may be missing a valid bin configuration in package.json.

Example:

"bin": {
  "kdm": "./bin/cli.js"
}

Additionally, the CLI entry file should begin with:

#!/usr/bin/env node

---

Suggested Fix

• Add a proper bin field in package.json
• Ensure the CLI entry file path is correct
• Ensure the CLI file is executable
• Republish the package after updating the configuration

---

Installation Logs

npm install -g kdm-cli@latest

changed 267 packages in 12s

Then:

kdm

Result:

Command 'kdm' not found

[utkarsh232005]

@CodeRabbit plan

[coderabbitai]

Coding Plan

Summary

• Leverage tsup's --banner.js flag to inject the Node.js shebang (#!/usr/bin/env node) directly into the compiled dist/index.js output
• Update the bin field in package.json to point to ./dist/index.js instead of the non-existent ./bin/kdm.js
• Remove the unused bin directory reference from both the files array and .gitignore
• The existing prepublishOnly script ensures the build runs before npm publish, so no additional publish workflow changes are needed

Design Choices

Design Choice 1: CLI entry point strategy

Options Considered:

1. Point bin directly to dist/index.js and inject shebang via tsup's --banner flag during build
2. Create a static bin/kdm.js wrapper file that imports the compiled output, and commit it to the repository

Chosen Option: 1

Rationale: Using tsup's banner injection keeps everything in the build pipeline, eliminates the need for a separate wrapper file, and follows modern CLI packaging conventions where the compiled output serves directly as the executable.

💡 User Tips

Regenerate the plan with different choices with @coderabbitai <feedback>.

Implementation Steps

Fix CLI Binary Configuration

This phase addresses the root cause by ensuring the build process produces a valid executable entry point and that package.json references the correct file path.

Task 1: Configure tsup to produce an executable CLI entry point

Enable shebang injection in the build process so the compiled output can be executed directly as a CLI.

• Modify the build script in package.json to add the --banner.js flag with the Node.js shebang (#!/usr/bin/env node)
• Apply the same banner flag to the dev script for consistency during local development
• The shebang will be prepended to dist/index.js automatically during each build

Task 2: Update package.json bin and files fields

Correct the bin configuration to reference the actual compiled output location.

• Change the bin field from "./bin/kdm.js" to "./dist/index.js" since the build output is the direct entry point
• Update the files array to remove "bin" since that directory is no longer used; the array should contain ["dist", "README.md", "LICENSE"]

Task 3: Clean up obsolete configuration

Remove configuration artifacts that no longer apply to prevent future confusion.

• Remove the ./bin entry from .gitignore since the bin directory approach is being abandoned in favor of direct dist/ usage

🤖 Prompt for AI agents

This phase fixes the broken `kdm` CLI binary by configuring the build pipeline
to produce a valid executable entry point and updating `package.json` to
reference the correct output file.

- In `package.json`, update the `build` script to add the `--banner.js
'#!/usr/bin/env node'` flag to the tsup command so the shebang is prepended to
`dist/index.js` on every build
- Apply the same `--banner.js` flag to the `dev` script for consistency during
local development
- In `package.json`, change the `bin` field value from `"./bin/kdm.js"` to
`"./dist/index.js"`
- In `package.json`, update the `files` array to remove the `"bin"` entry; the
array should only contain `["dist", "README.md", "LICENSE"]`
- In `.gitignore`, remove the `./bin` entry since the bin directory approach is
no longer used

Research

This is an ESM-native CLI package using Commander.js for command parsing, with some commands using Ink/React for TUI rendering. The build system uses tsup to bundle src/index.ts into dist/index.js. The CLI bootstraps via src/commands/root.ts which configures Commander and registers subcommands (show, health, watch, logs, config). Currently, the bin field in package.json points to a non-existent ./bin/kdm.js file that is git-ignored and never generated by the build process.

---

🚀 Next Steps

🤖 All AI agent prompts combined

This phase fixes the broken `kdm` CLI binary by configuring the build pipeline
to produce a valid executable entry point and updating `package.json` to
reference the correct output file.

- In `package.json`, update the `build` script to add the `--banner.js
'#!/usr/bin/env node'` flag to the tsup command so the shebang is prepended to
`dist/index.js` on every build
- Apply the same `--banner.js` flag to the `dev` script for consistency during
local development
- In `package.json`, change the `bin` field value from `"./bin/kdm.js"` to
`"./dist/index.js"`
- In `package.json`, update the `files` array to remove the `"bin"` entry; the
array should only contain `["dist", "README.md", "LICENSE"]`
- In `.gitignore`, remove the `./bin` entry since the bin directory approach is
no longer used

💡 Iterate on the plan with: @coderabbitai <feedback>

Example Feedback
- `@coderabbitai` You can skip phase 3. Add a simple unit test case for phase 2.
- `@coderabbitai` For design choice 1 go ahead with option 3 and replan.

---

💬 Have feedback or questions? Drop into our discord!