Using ChatGPT to Fix Node.js Runtime Checks and Eliminate CLI Side Effects

Problem Statement

An engineer developing the ZenStack toolkit—built on Next.js, TypeScript, and Prisma—needed a way to verify at runtime that Node.js (and consequently Prisma) was installed before the CLI could proceed.

ChatGPT's Initial Answer

The developer asked ChatGPT for a solution and received a concise, convincing answer that resolved the immediate issue.

Side Effects Encountered

While the solution worked, it introduced a side effect: the CLI used async-exit-hook to handle uncaught errors, which caused additional code (including Prisma imports) to execute unintentionally, making the behavior unpredictable.

// You can hook uncaught errors with uncaughtExceptionHandler(), consequently adding
// async support to uncaught errors (normally uncaught errors result in a synchronous exit).
exitHook.uncaughtExceptionHandler(err => {
    console.error(err);
});

Cleaner Approach with Child Processes

To avoid these side effects, the recommended strategy was to run the check in a separate child process using Node's child_process module, isolating any unintended execution.

Exploring npm for Module Information

The developer then investigated how npm determines a package's version. By creating a dummy package with a package.json file, they could query npm for the installed version.

{
    "name": "dummy-package",
    "version": "9.9.9"
}

Running the command: npm list --depth=0 dummy-package produced output showing the package and its version:

[email protected] /Users/jiasheng/branch/helloworld
└── [email protected] extraneous

Using Package JSON Directly

Instead of invoking npm, the developer could directly require the package's package.json to obtain version information without side effects:

const prisma:any = require('prisma/package.json');

This method eliminates the unwanted side effects while providing detailed package metadata.

Conclusion

ChatGPT proved to be a valuable assistant for quickly generating code solutions, but developers must still apply critical thinking and thorough testing to ensure clean, maintainable implementations.