Unverified Commit 13ebfe40 authored by Noemi's avatar Noemi Committed by GitHub

Add `@appsignal/nodejs` to the external packages list (#64503)

The `@appsignal/nodejs` instrumentation package fails to load in Next.js
14 due to Webpack failing to bundle its Node.js native extension. Adding
it to the server components external packages list fixes this issue.

Part of https://github.com/appsignal/appsignal-nodejs/issues/1014.
parent 792b8485
...@@ -20,6 +20,7 @@ module.exports = nextConfig ...@@ -20,6 +20,7 @@ module.exports = nextConfig
Next.js includes a [short list of popular packages](https://github.com/vercel/next.js/blob/canary/packages/next/src/lib/server-external-packages.json) that currently are working on compatibility and automatically opt-ed out: Next.js includes a [short list of popular packages](https://github.com/vercel/next.js/blob/canary/packages/next/src/lib/server-external-packages.json) that currently are working on compatibility and automatically opt-ed out:
- `@appsignal/nodejs`
- `@aws-sdk/client-s3` - `@aws-sdk/client-s3`
- `@aws-sdk/s3-presigned-post` - `@aws-sdk/s3-presigned-post`
- `@blockfrost/blockfrost-js` - `@blockfrost/blockfrost-js`
......
[ [
"@appsignal/nodejs",
"@aws-sdk/client-s3", "@aws-sdk/client-s3",
"@aws-sdk/s3-presigned-post", "@aws-sdk/s3-presigned-post",
"@blockfrost/blockfrost-js", "@blockfrost/blockfrost-js",
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment