-
Notifications
You must be signed in to change notification settings - Fork 306
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
Feature Request: Bun Support #3749
Comments
Btw, I also reported the same issue in Bun repo oven-sh/bun#6374 |
For anyone looking for a way to enable DD tracing in a Bun runtime - there's a (hacky) way to do so (see gist https://gist.github.com/Koka/f1801289b526eeb5853894cc4e3e747d) Short summary - I had to monkey patch dogstatsd.CustomMetrics to avoid sending metrics through UDP (not supported by Bun runtime yet) and add a shim BlockList to node net module (blocklist is not supported by Bun runtime yet and shim is built in but detection doesn't play well with Bun) Using this technique you can run functional APM tracing without any metrics being sent, and without any integrations, so you have to call tracer.trace manually |
Relevant PRs: We manually tested it works when using Express and CommonJS. I don't think it supports tracing ESM imports, as we haven't implemented the Node.js loader API (though we do support a module loader API which works both with CommonJS & ESM without extra work to support both) |
Is there an issue for tracking support for tracing ESM imports? |
Is there an example for this integration somewhere you could share please? I followed the different options from the official Datadog documentation here, but no luck so far. |
Hi, I'm trying to run my app with Bun but I'm getting this error and it seems the root cause is the package of dd-trace. I know this is not your responsibility to fix this kind of issues, however, I wonder if there's any chance you take a look in case you can support the Bun project by fixing the problem from your side or giving feedback about what is the incompatibility issue with this library and Bun.
Expected behaviour
Start the Nestjs server successfully with Bun.
NPM script:
"start": "NODE_ENV=localdev nest start --watch --exec "bun run"",
Actual behaviour
It's throwing the following error when starting a Nest.js app:
Steps to reproduce
ddt-trace
with Bun 1.0.8Have the start script as:
"start": "NODE_ENV=localdev nest start --watch --exec "bun run"",
Environment
The text was updated successfully, but these errors were encountered: