package.json is currently private:true with no name scope, bin, exports, or files field. Decide the publish-shaped values now (package name/scope, bin entry name(s) for npx, exports field, files allowlist, engines) even though we won't publish yet — this depends on the build strategy decision (issue #3) since files/engines differ depending on whether dist/ ships or source .ts ships.
Part of [TypeScript project conventions for delegate-ai-mcp](https://git.arthurerlich.de/haylan/delegate-ai-mcp/issues/1)
Blocked by [Build & typecheck strategy for delegate-ai-mcp](https://git.arthurerlich.de/haylan/delegate-ai-mcp/issues/3)
## Question
package.json is currently private:true with no name scope, bin, exports, or files field. Decide the publish-shaped values now (package name/scope, bin entry name(s) for npx, exports field, files allowlist, engines) even though we won't publish yet — this depends on the build strategy decision (issue #3) since files/engines differ depending on whether dist/ ships or source .ts ships.
Closed as out of scope: this ticket assumed a real npm-publish eventually happens, but the no-build decision (ticket #3, reverted to no-build) means native strip-types can't run from inside node_modules — Node hard-errors on it. There's nothing to publish-shape until/unless a future decision reopens the build question. Deferred back to the map's fog.
Closed as out of scope: this ticket assumed a real npm-publish eventually happens, but the no-build decision (ticket #3, reverted to no-build) means native strip-types can't run from inside node_modules — Node hard-errors on it. There's nothing to publish-shape until/unless a future decision reopens the build question. Deferred back to the map's fog.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Part of TypeScript project conventions for delegate-ai-mcp
Blocked by Build & typecheck strategy for delegate-ai-mcp
Question
package.json is currently private:true with no name scope, bin, exports, or files field. Decide the publish-shaped values now (package name/scope, bin entry name(s) for npx, exports field, files allowlist, engines) even though we won't publish yet — this depends on the build strategy decision (issue #3) since files/engines differ depending on whether dist/ ships or source .ts ships.
haylan referenced this issue2026-09-06 14:42:45 +00:00
Closed as out of scope: this ticket assumed a real npm-publish eventually happens, but the no-build decision (ticket #3, reverted to no-build) means native strip-types can't run from inside node_modules — Node hard-errors on it. There's nothing to publish-shape until/unless a future decision reopens the build question. Deferred back to the map's fog.