tsedio / tsedio/tsed-cli

@tsed/cli-mcp package declares tsed-mcp bin but published files are missing

Open
#568 4 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
TypeScript
Stars
43
Forks
24
Avg merge
27m
Merged PRs (30d)
1

Description

Summary

@tsed/cli-mcp@7.5.1 documents and declares a tsed-mcp binary, but the published npm package does not include the bin target files, so the command cannot be executed via npx or after install.

Reproduction

npx --yes --package @tsed/cli-mcp@7.5.1 tsed-mcp --help

Actual result:

sh: tsed-mcp: command not found

I also checked a clean install:

mkdir /tmp/tsed-cli-mcp-repro
cd /tmp/tsed-cli-mcp-repro
npm install --ignore-scripts --no-audit --no-fund @tsed/cli-mcp@7.5.1
ls node_modules/@tsed/cli-mcp/lib/esm/bin

Actual result:

ls: node_modules/@tsed/cli-mcp/lib/esm/bin: No such file or directory

What I expected

The command documented in packages/cli-mcp/readme.md should start the MCP CLI/server entrypoint:

npx tsed-mcp

What looks wrong

The published @tsed/cli-mcp package declares:

"bin": {
  "tsed": "lib/esm/bin/tsed.js",
  "tsed-mcp": "lib/esm/bin/tsed-mcp.js"
}

but the package tarball only contains the library files under lib/esm and lib/types; there is no lib/esm/bin/tsed.js or lib/esm/bin/tsed-mcp.js.

The repo source also appears to have no packages/cli-mcp/src/bin entrypoint to compile into those paths.

Environment

  • Package: @tsed/cli-mcp@7.5.1
  • Node: v26.0.0
  • npm: 11.12.1
  • OS: macOS

Contributor guide

Open the 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.

Research direction

Start with packages/cli-mcp/readme.md and the package configuration declaring the tsed and tsed-mcp bin targets. Inspect packages/cli-mcp/src/bin and reproduce the clean install or npx command; done means the published package contains the declared targets and npx tsed-mcp starts successfully.

Written by the indexing model from the issue text.

Assessment

Tech stack
node.js, typescript
Domain
build-system, cli
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
58/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.