IgniteUI / igniteui-cli / 41976078116

95%

push

github

perf(cli): start the MCP server in-process before the CLI loads (#1871)

* perf(cli): start the MCP server in-process before the CLI loads

`ig mcp` loaded the whole CLI (yargs, every template) and then spawned
the server as a second Node process. bin/execute.js now finds the
server installed with the selected CLI copy and imports it directly,
which halves the warm start (about 1.1 s to 0.45 s) and runs one
process per session. Help, version, other options and a missing or
unbuilt server still go through the CLI.

The server lookup follows the CLI copy's real path, so it works in
pnpm projects. The global/local version notice now goes to stderr, as
stdout carries the MCP protocol.

* test(cli): kill a hung MCP server in the acceptance spec

The spec now has its own deadline, shorter than the Jasmine timeout,
that kills the child and rejects, so a server that never answers
initialize or never exits doesn't outlive the spec.

* test(cli): check that ig mcp sends docs requests to the --remote backend

The remote specs started the server against an unreachable URL and
only checked the initialize reply, which local mode returns too.
They now call list_components against a local HTTP fixture and
assert that the fixture received the request and that its response
reaches the tool result, for both --remote=<url> and --remote <url>.

---------

Co-authored-by: Konstantin Dinev <kdinev@bellumgens.com>

1717 of 1994 branches covered (86.11%)

Branch coverage included in aggregate %.

33 of 36 new or added lines in 2 files covered. (91.67%)

9400 of 9663 relevant lines covered (97.28%)

181.75 hits per line