Plans to support nextjs app router middleware feature to v14 or higher

[eliabecardoso]

Plans to support nextjs middleware for app router v14 or higher

Hello, do you have any plans to support nextjs middleware feature in stable version 14 or higher?
Or enable it by a provided parameter?

I have an app with:

"newrelic": "12.11.1"
"next": "14.2.23"

When I was setting up newrelic on my nextjs app, I received the message log:

{"v":0,"level":40,"name":"newrelic","hostname":"eliabe-cardoso","pid":530631,"time":"2025-01-16T03:25:19.442Z","msg":"Next.js middleware instrumentation only supported on >=12.2.0 <=13.4.12, got 14.2.3","component":"WebFrameworkShim","module":"next/dist/server/next-server","framework":"Nextjs"}

Now I have already configured newrelic in the project, but the APM of this service without monitoring middleware is weak and with few data metrics than I expected.

Reference: https://github.com/newrelic/node-newrelic/blob/main/lib/instrumentation/nextjs/utils.js#L34-L58

[workato-integration]

https://new-relic.atlassian.net/browse/NR-359746

[bizob2828]

@eliabecardoso In Next.js 13.4.12+ middleware runs in a worker thread. Our agent does not propagate between the main and worker threads so there's nothing useful that would happen here. For use cases like this we recommend you rely on Next.js native opentelemetry spans and load them to New Relic via OTLP, see FAQ

[eliabecardoso]

@bizob2828 hello!

Oh, I didn't know, thanks for your quick reply and sharing an option to workaround this.
So I'll implement via OTLP!