Connor Pearson
Connor Pearson
Is this the same issue as https://github.com/nuxt/nuxt/issues/18909? Does [this solution](https://github.com/nuxt/nuxt/issues/18909#issuecomment-1425016833) work?
> Would you see if you can reproduce this in pure Nitro ([reproduction sandbox](https://stackblitz.com/github/unjs/nitro/tree/main/examples/hello-world)), and if so, raise [there](https://github.com/unjs/nitro/issues/new/choose)? 🙏 I've added a nitro [reproduction](https://github.com/cjpearson/nitro-externals-test) and [issue](https://github.com/nitrojs/nitro/issues/3100).
We've been using a manual OpenTelemetry instrumentation for our projects and the idea of having an officially supported version is exciting! Have you given any thought to supporting [Native Instrumentation](https://opentelemetry.io/docs/languages/js/libraries/#use-natively-instrumented-libraries)...
Oh cool. Are you open to PRs in this direction?
I've created a basic reproduction [here](https://stackblitz.com/edit/github-jpkcwc?file=server%2Froutes%2Findex.ts). It has a single route with a max age of 10 seconds and stale max age of 30 seconds. On the initial request, the...
For a reproduction you can use the starter app and adjust the config: ```ts // https://nitro.unjs.io/config export default defineNitroConfig({ srcDir: "server", storage: { redis: { driver: "redis", url: "redis://localhost:6379", maxRetriesPerRequest:...
@pi0 I think this can be marked as fixed
I wanted to use the esnext build to get the newer compilation target, since rollup also complains about the global `this` that is present in the esm build. So bumping...
I've created an example here: https://github.com/cjpearson/nuxt-otel-repro Nuxt uses several plugins, so it's probably possible to narrow it down further if needed. But this app adds a single endpoint which imports...