ponytail-mcp/package.json: no main or exports field

[nanaubusiness]

In ponytail-mcp/package.json, there is no main or exports field. The index.js is not reachable via npm module resolution (e.g., require('@dietrichgebert/ponytail/ponytail-mcp')). Users following the README MCP setup instructions work around this by pointing config directly at the file, but package-level imports would fail.

[nanaubusiness]

Duplicate of #376.

[nanaubusiness]

Reopening — corresponding PR is under review.

[DietrichGebert]

Closing as not applicable. ponytail-mcp is a private ("private": true), ESM ("type": "module") MCP server that is spawned as a process, not imported. The README launches it by path: { "command": "node", "args": ["ponytail-mcp/index.js"] }, and index.js has a #!/usr/bin/env node shebang and speaks MCP over stdio.

main / exports are module-resolution hints for require/import. Nothing imports this package, so there is no resolution path to fix. The example here, require("@dietrichgebert/ponytail/ponytail-mcp"), is not a real usage pattern and would not work anyway (ESM cannot be require`d, and the subdir is private). Adding those fields would be metadata for an import that does not exist.