-
Notifications
You must be signed in to change notification settings - Fork 2.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
support node:inspector
#2445
Comments
We do plan on having a better debugging experience, which might include import { url } from "inspector";
// ...
const isDebugging = () => !!url(); In the interim, we should consider adding a no-op polyfill. cc @Jarred-Sumner |
I know this is a mess of lockfiles, should be fine once we get oven-sh/bun#2445
@Electroid I want to flag another possible use case for something similar to As an orthogonal task to this we are also looking into Bun. So... Marrying the two concepts here: Is there a way to do what we want in Bun today? Perhaps via some 'bun:inspector' API, or via JavaScriptCore directly perhaps? |
Is it possible to write a polyfill for it so that i can use typedoc with bun or is this something that needs to be fixed on buns side? |
In our case we have decided against this feature as it was a significant cost to scan the JS heap looking for promises. It was so slow there is no way we can afford to run it in prod. Now, if there was a simple atomic counter counting the promises in the micro task queue that would be much more efficient. IDK how feasible that would be. |
This error comes up when trying to run |
I also get this error when trying to compile my docs via Typedoc. |
+1, same with |
Also hit this trying to use typedoc. |
From pm2 log-rotate
|
also running into this issue with vitest ui mode
|
What is the problem this feature would solve?
Due to lacking support of
node:inspector
, our bun projects cannot support typedoc. This is very troubling as we own a significant amount of repos and rely on typedoc to generate all-in-one documentation.What is the feature you are proposing to solve the problem?
Support
inspector
or having alternative way to walk around.What alternatives have you considered?
No response
The text was updated successfully, but these errors were encountered: