You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When adding Sentry configuration to next.config.ts using withSentryConfig, I encounter the following warning during the build process:
<w> [webpack.cache.PackFileCacheStrategy] Serializing big strings (318kiB) impacts deserialization performance (consider using Buffer instead and decode when needed)
Is this a known issue? Are there any recommendations for addressing this warning, such as additional configuration options or workarounds?
The following warning appears during the build process:
<w> [webpack.cache.PackFileCacheStrategy] Serializing big strings (318kiB) impacts deserialization performance (consider using Buffer instead and decode when needed)
The text was updated successfully, but these errors were encountered:
Could you please provide a reproduction repo? I tried setting up a new nextjs project using npx create-next-app@latest and setting Sentry up using npx @sentry/wizard@latest -i nextjs but did not run into any such warnings.
Is there an existing issue for this?
How do you use Sentry?
Sentry Saas (sentry.io)
Which SDK are you using?
@sentry/nestjs
SDK Version
8.50.0
Framework Version
React 19.0.0, Next 15.1.4, Node 22.9.0
Link to Sentry event
No response
Reproduction Example/SDK Setup
Description
When adding Sentry configuration to
next.config.ts
usingwithSentryConfig
, I encounter the following warning during the build process:Is this a known issue? Are there any recommendations for addressing this warning, such as additional configuration options or workarounds?
Thank you!
Steps to Reproduce
Start with a minimal
next.config.ts
file:Update the file to include Sentry's configuration using
withSentryConfig
:Run the build process.
Expected Result
The build completes without warnings or errors.
Actual Result
The following warning appears during the build process:
The text was updated successfully, but these errors were encountered: