getsentry / getsentry/sentry-javascript

Cloudflare events have no runtime version and no server name

Open
#24,040 1 comment 0 reactions 0 assignees View on GitHub
Cloudflare Workers Improvement javascript
Dominant language
TypeScript
Stars
8.7k
Forks
1.8k
Avg merge
1d 17h
Merged PRs (30d)
515

Description

`packages/cloudflare/src/client.ts:55`:

```ts
// TODO: Grab version information
runtime: { name: 'cloudflare' },
// TODO: Add server name
```

Bun reports `{name:'bun', version:'1.3.14'}` and Deno reports the Deno version. Cloudflare reports neither a version nor a `server_name`, so events cannot be grouped or filtered by worker.

**Work item.** Set `server_name` from the script name where it is available (`env` binding metadata or the wrangler-injected name). For the version, either use the compatibility date if reachable at runtime or delete the TODO with a note saying workerd exposes nothing usable.

Contributor guide

Open the contributing guide

Research direction

Start at packages/cloudflare/src/client.ts:55 and review the existing runtime metadata alongside the Bun and Deno behavior mentioned in the issue. Trace which script-name metadata is available through env binding metadata or the wrangler-injected name, and determine whether the compatibility date is reachable at runtime. Done means Cloudflare events report server_name when available and either a usable version or a note explaining why workerd cannot provide one.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
cloud, observability
Issue type
Feature
Difficulty
3/5
Estimated time
1-2 days
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
70/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.