Skip to content

fix: restore code analyzer ingest - #206

Merged
brianhdk merged 1 commit into
mainfrom
agent/fix-code-analyzer-ingest
Aug 4, 2026
Merged

fix: restore code analyzer ingest#206
brianhdk merged 1 commit into
mainfrom
agent/fix-code-analyzer-ingest

Conversation

@mzanoni

@mzanoni mzanoni commented Aug 3, 2026

Copy link
Copy Markdown
Contributor

https://trello.com/c/imUcysvy/21187-js-sdk-mcp-integration-is-failing

Summary

  • Add Node type definitions to packages/code-analyzer and explicitly include Node types in its TypeScript config.
  • Fix stricter TypeScript compile errors in analyzer handlers exposed by the upgraded toolchain.
  • Keep the generated ingestion payload shape aligned with the analyzer model types by omitting optional values instead of writing null where the model does not allow it.

Root Cause

The MCP ingest workflow runs ts-node ./src/main.ts, which uses Node APIs (fs, process) but code-analyzer did not declare Node typings directly or include them in tsconfig.json. After dependency updates, transitive Node globals were no longer available. The newer TypeScript/tooling also surfaced existing null/undefined mismatches in handler return objects.

Validation

  • npm --prefix .\packages\code-analyzer run codeAnalyzer -- '..\client\tsconfig.json' '@relewise/client'
  • npm --prefix .\packages\code-analyzer run codeAnalyzer -- '..\integrations\tsconfig.json' '@relewise/integrations'
  • npm --prefix .\packages\code-analyzer run lint
  • npm --prefix .\packages\code-analyzer audit --audit-level=low

@mzanoni
mzanoni marked this pull request as ready for review August 4, 2026 05:40
@mzanoni
mzanoni requested a review from brianhdk August 4, 2026 05:40
@brianhdk
brianhdk merged commit 04a696a into main Aug 4, 2026
4 checks passed
@brianhdk
brianhdk deleted the agent/fix-code-analyzer-ingest branch August 4, 2026 05:42
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants