Skip to content

Add Remix 3 TracingChannel proposal#1

Open
sergical wants to merge 2 commits into
getsentry:mainfrom
sergical:proposal/remix
Open

Add Remix 3 TracingChannel proposal#1
sergical wants to merge 2 commits into
getsentry:mainfrom
sergical:proposal/remix

Conversation

@sergical

@sergical sergical commented May 4, 2026

Copy link
Copy Markdown
Member

Summary

  • Adds proposals/remix.md — TracingChannel proposal for Remix 3 covering three channels:
    • remix:request — middleware and route handler tracing in fetch-router
    • remix:render — server-side rendering in ui/server
    • remix:asset — on-demand script/style compilation in assets
  • Updates TRACKER.md with Remix entry

Context

Remix 3 is a ground-up rewrite with a Fetch API-native architecture. No existing APM instrumentation exists for it, making this a greenfield opportunity to ship TracingChannel from day one.

A working implementation exists at sergical/remix#1 with a demo app that sends spans to Sentry via otel-tracing-channel.

🤖 Generated with Claude Code

Proposes three channels for Remix 3's three subsystems:
- remix:request — middleware and route handler tracing in fetch-router
- remix:render — server-side rendering in ui/server
- remix:asset — on-demand script/style compilation in assets

Remix 3 is a greenfield framework with no existing APM instrumentation,
making this a rare opportunity to ship TracingChannel from day one.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants