Schweiz
Joined on 2025-05-30
Block a user
Set up Gitea Actions: build, test, and publish delegate-ai-mcp to this repo's package registry
Set up Gitea Actions: build, test, and publish delegate-ai-mcp to this repo's package registry
Closed as out of scope: this ticket depended on ticket #3's 'build now' decision, which was reverted. User wants to keep writing TypeScript directly with no build process, so there's nothing to…
Build & typecheck strategy for delegate-ai-mcp
Build & typecheck strategy for delegate-ai-mcp
Reopened and revised: reverting the build-now decision.
Final answer: no build process at all. Keep running src/*.ts directly via Node's native TS type-stripping, exactly as before ticket #3's…
Build & typecheck strategy for delegate-ai-mcp
Set up Gitea Actions: build, test, and publish delegate-ai-mcp to this repo's package registry
Build & typecheck strategy for delegate-ai-mcp
Build & typecheck strategy for delegate-ai-mcp
Resolved: adopt the official MCP quickstart's own defaults, build now (not deferred).
- tsconfig.json: target ES2022, module/moduleResolution Node16, strict: true, outDir ./build, rootDir ./src,…
How do TS MCP servers conventionally handle build, types, and publishing?
How do TS MCP servers conventionally handle build, types, and publishing?
Findings on branch research/ts-mcp-conventions (research/ts-mcp-project-conventions.md): tsc-to-dist is the de facto build standard (official SDK v1 + all example servers + real third-party…
Publish-shaped package.json for delegate-ai-mcp
Lint/format tooling for delegate-ai-mcp
Multi-tool source structure for delegate-ai-mcp
Build & typecheck strategy for delegate-ai-mcp
How do TS MCP servers conventionally handle build, types, and publishing?
TypeScript project conventions for delegate-ai-mcp