Skip to content

test(nuxt): Test mysql instrumentation with orchestrion bundler plugin#21782

Merged
s1gr1d merged 8 commits into
developfrom
sig/nuxt-4-orchestrion
Jun 26, 2026
Merged

test(nuxt): Test mysql instrumentation with orchestrion bundler plugin#21782
s1gr1d merged 8 commits into
developfrom
sig/nuxt-4-orchestrion

Conversation

@s1gr1d

@s1gr1d s1gr1d commented Jun 25, 2026

Copy link
Copy Markdown
Member

Adds a Nuxt 4 E2E test app that shows how orchestrion (build-time diagnostics_channel injection) can be wired into a meta framework, so DB instrumentation works on bundled server code without --import.

  • Rollup plugin instead of Vite. Nuxt's server is built by Nitro (Rollup), so the orchestrion code transform is wired in as a Nitro Rollup plugin, mirroring the existing Vite plugin.

  • Local module to inject init to "server entry". Nitro does not expose an explicit server entry to place the Sentry init in. A small local Nuxt module (mirroring @sentry/nuxt's addSentryTopImport) injects a top-level import './sentry.server.config.mjs' into Nitro's built entry, so node .output/server/index.mjs initializes Sentry first

  • Both instrumentation paths coexist. orchestrion handles the bundled mysql (auto.db.orchestrion.mysql), while OTel keeps instrumenting everything left external (ioredis, http, …)

@s1gr1d s1gr1d requested review from mydea and nicohrubec June 25, 2026 11:08
@s1gr1d s1gr1d changed the title test(nuxt): Test mysql instrumentation with orchestrion test(nuxt): Test mysql instrumentation with orchestrion bundler plugin Jun 26, 2026
return;
}

writeFileSync(entryFilePath, topImport + data, 'utf8');
@s1gr1d s1gr1d requested review from isaacs and timfish June 26, 2026 09:12
@s1gr1d s1gr1d merged commit 9af2819 into develop Jun 26, 2026
282 of 284 checks passed
@s1gr1d s1gr1d deleted the sig/nuxt-4-orchestrion branch June 26, 2026 13:15
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.

3 participants