Skip to content

Support for Deno server #3009

Description

@mhmo91

Summary

SDK For https://deno.land/

A Deno SDK would require Sentry provides a package which follows the spec upon which Deno applications are built. Essentially it is based on a non-node JS runtime. To some extend the existing JS SDK can already run in such runtimes with recent changes post v7 (Vercel Edge for example)

    - Handling imports/dependencies (imports & lack of package.json)
### Install
- [x] ```sentry@deno```
- [x] Publish on deno registry
### Product
- [x] Errors
- [x] Performance
- [x] Manual: Existing SDK API
- [x] Automatic: Expect to use existing HTTP, ORM, DB integrations for Node
- [x] Distributed Tracing: [Dynamic Sampling Context](https://develop.sentry.dev/sdk/performance/dynamic-sampling-context/) & Tracing without Performance
- [x] Event Context: Shall follow [Sentry SDK Spec](https://develop.sentry.dev/sdk/event-payloads/contexts/)

Open Points:

  • Are there any specific around transaction naming conventions or similar which would be natively better to Deno, than Node for example?
    • Specifics around span operation naming conventions? (HTTP, DB, rpc, etc)

Metadata

Metadata

Assignees

Labels

No labels
No labels

Projects

Status
No status

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions