Devotd Github
NewModel Context Protocol

alpic-ai/skybridge — Removing the DEP0190 warning in skybridge dev

alpic-ai/skybridge changes how the type check is run in `skybridge dev` to eliminate Node.js's upcoming-deprecation warning DEP0190, and handles process start failure with a console message.

Repositoryalpic-ai/skybridge ↗

alpic-ai/skybridge changes how the type check is run in `skybridge dev` to eliminate Node.js's upcoming-deprecation warning DEP0190, and handles process start failure with a console message.

GitHub description: Skybridge is a full-stack TypeScript framework for MCP Apps and ChatGPT Apps. Type-safe. React-powered. Platform-agnostic.

stars
★ 2.2K
Forks
141
Language
TypeScript
License
MIT
Latest release
v2.0.4
Read original source ↗View on GitHub ↗

alpic-ai/skybridge is a full-stack TypeScript framework for MCP (Model Context Protocol) apps and ChatGPT apps. The repository description states that it is type-safe, React-based, and platform-agnostic. The GitHub commit 9afa5fa (#965) from October 29, 2026 is a fix that removes the one warning that appeared in `skybridge dev`. The only file changed is `packages/core/src/cli/use-typescript-check.ts`, and it comes to 11 added lines and 4 deleted lines.

That file launches `npx tsc --noEmit --watch --pretty false` as a child process while the dev server is running, collecting type errors and passing them along. `--noEmit` means to produce no output files and show only errors, and `--watch` means to re-check every time a file changes. The existing code ran it with `shell: true` while appending the arguments to a single-line string, and Node.js was issuing the upcoming-deprecation warning DEP0190 for that approach. This patch splits the invocation into `npx` and an array of arguments and removes the `shell` option, so the warning no longer appears. The `error` event handler included alongside it leaves a `TypeScript watcher failed to start` message on the console if the type check process itself fails to start. The part that collects and passes on the errors is unchanged.

That said, this commit is not a feature addition but an internal CLI maintenance fix, and this record contains no information about a new version or release notes. Repository basics such as the license or the level of interest are also not given, so it is hard to judge the impact of the change on the framework as a whole. From the point of view of someone using `skybridge dev`, the confirmable result is limited to the console noise disappearing and start failures surfacing as messages, and whether to use this framework has to be judged together with other evidence.