Is there a way to view active resources keeping the Deno event loop open?
I'm trying to debug a Deno process mysteriously staying alive when it should close. Is there an equivalent of the getActiveResourcesInfo API from node? When I try to do
import { getActiveResourcesInfo } from 'node:process'; in Deno I get the error Uncaught SyntaxError: The requested module 'node:process' does not provide an export named 'getActiveResourcesInfo' so it looks like this particular API is unimplemented in Deno. I've also tried looking around in the inspector using deno run --inspect but I can't find any way to see the active resources there.2 Replies
GitHub
denoland/deno
A modern runtime for JavaScript and TypeScript. Contribute to denoland/deno development by creating an account on GitHub.
I'll think about it, consolidating the code into a format that I can share easily may be tricky