Next js production backend source maps #224
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Enable source mapping in Next.js
For source-mapped backtraces to be emitted for Next.js backend errors
when Next.js is running in production mode, the webpack configuration
needs to be tweaked in order to emit backtraces, and the
--enable-source-maps
flag needs to be passed to the Node.js runtimewhen starting the Next.js application, using the
NODE_OPTIONS
environment variable.
Do not lock AppSignal version for Next.js
The Next.js test setups, due to a Webpack limitation, do not use the
source code of the integration at
nodejs/integration
, insteadinstalling it from the NPM servers.
Due to this, it makes sense for its bound to be set to
latest
, toprevent accidentally testing against a very old version of the
integration.