Releases: newrelic/newrelic-node-nextjs
v0.3.0
v0.3.0 (2022-07-27)
- BREAKING Removed support for Node 12.
The minimum supported version is now Node v14. For further information on our support policy, see: https://docs.newrelic.com/docs/agents/nodejs-agent/getting-started/compatibility-requirements-nodejs-agent.
-
Added support for Node 18.x
-
Updated sample app to use
http.get
instead offetch
to make subrequests to API to avoid async context propagation breakage in Node 18.
Support statement:
- New Relic recommends that you upgrade the agent regularly to ensure that you're getting the latest features and performance benefits. Additionally, older releases will no longer be supported when they reach end-of-life.
v0.2.0
-
BREAKING: Fixed instrumentation to only support middleware in
>=12.2.0
of Next.js- Next.js has made middleware stable.
- All attempts in
@newrelic/next
to track middleware before 12.2.0 have been removed.
-
Added an additional path to register
next-server
when running a Next.js app with a standalone server. -
Updated dev-dependencies to clear security audit warnings.
v0.1.1
-
Added support for middleware in > 12.1.1 of Next.js. The return of
getModuleContext
is now an async function. -
Fixed a few small documentation items.
v0.1.0
- Initial release of the Node.js Next.js instrumentation.
- Transaction naming based on Next.js page or API route.
- Segment/Span capture for middleware, and getServerSideProps.
- Documentation around manually injecting the New Relic browser agent.
- Verified support on Next.js >= 12.0.9