-
-
Notifications
You must be signed in to change notification settings - Fork 1.7k
Closed
Labels
Package: nextjsIssues related to the Sentry Nextjs SDKIssues related to the Sentry Nextjs SDK
Description
Is there an existing issue for this?
- I have checked for existing issues https://github.com/getsentry/sentry-javascript/issues
- I have reviewed the documentation https://docs.sentry.io/
- I am using the latest SDK release https://github.com/getsentry/sentry-javascript/releases
How do you use Sentry?
Self-hosted/on-premise
Which SDK are you using?
@sentry/nextjs
SDK Version
7.61.0
Framework Version
Next 13.4.12
Link to Sentry event
No response
SDK Setup
client:
Sentry.init({
dsn: 'REDACTED',
// Adjust this value in production, or use tracesSampler for greater control
tracesSampleRate: 1,
// Setting this option to true will print useful information to the console while you're setting up Sentry.
debug: false,
replaysOnErrorSampleRate: 1.0,
// This sets the sample rate to be 10%. You may want this to be 100% while
// in development and sample at a lower rate in production
replaysSessionSampleRate: 0.0,
// You can remove this option if you're not planning to use the Sentry Session Replay feature:
integrations: [
new Sentry.Replay({
// Additional Replay configuration goes in here, for example:
maskAllText: true,
blockAllMedia: true,
}),
],
enabled: !IS_DEV,
})edge and server:
Sentry.init({
dsn: 'REDACTED',
// Adjust this value in production, or use tracesSampler for greater control
tracesSampleRate: 1,
// Setting this option to true will print useful information to the console while you're setting up Sentry.
debug: false,
enabled: !IS_DEV,
})Steps to Reproduce
Just start the next project and visit the site
Expected Result
No errors/warnings
Actual Result
<w> [webpack.cache.PackFileCacheStrategy/webpack.FileSystemInfo] Resolving '@sentry/webpack-plugin/src/cjs' in <PATH_REPLACED>/node_modules/.pnpm/@sentry+utils@7.61.0/node_modules/@sentry/utils/cjs for build dependencies doesn't lead to expected result '<PATH_REPLACED>/node_modules/@sentry/webpack-plugin/src/cjs.js', but to '<PATH_REPLACED>/node_modules/.pnpm/@sentry+webpack-plugin@1.20.0/node_modules/@sentry/webpack-plugin/src/cjs.js' instead. Resolving dependencies are ignored for this path.
<w> at unknown 4 @sentry/webpack-plugin/src/cjs
<w> at file dependencies <PATH_REPLACED>/node_modules/.pnpm/@sentry+utils@7.61.0/node_modules/@sentry/utils/cjs/node.js
<w> at file <PATH_REPLACED>/node_modules/.pnpm/@sentry+utils@7.61.0/node_modules/@sentry/utils/cjs/node.js
<w> at file dependencies <PATH_REPLACED>/node_modules/.pnpm/@sentry+utils@7.61.0/node_modules/@sentry/utils/cjs/time.js
<w> at file <PATH_REPLACED>/node_modules/.pnpm/@sentry+utils@7.61.0/node_modules/@sentry/utils/cjs/time.js
<w> at file dependencies <PATH_REPLACED>/node_modules/.pnpm/@sentry+utils@7.61.0/node_modules/@sentry/utils/cjs/clientreport.js
<w> at file <PATH_REPLACED>/node_modules/.pnpm/@sentry+utils@7.61.0/node_modules/@sentry/utils/cjs/clientreport.js
<w> at file dependencies <PATH_REPLACED>/node_modules/.pnpm/@sentry+utils@7.61.0/node_modules/@sentry/utils/cjs/index.js
<w> at file <PATH_REPLACED>/node_modules/.pnpm/@sentry+utils@7.61.0/node_modules/@sentry/utils/cjs/index.js
<w> at file dependencies <PATH_REPLACED>/node_modules/.pnpm/@sentry+nextjs@7.61.0_next@13.4.12_react@18.2.0_webpack@5.88.2/node_modules/@sentry/nextjs/cjs/config/loaders/wrappingLoader.js
<w> at file <PATH_REPLACED>/node_modules/.pnpm/@sentry+nextjs@7.61.0_next@13.4.12_react@18.2.0_webpack@5.88.2/node_modules/@sentry/nextjs/cjs/config/loaders/wrappingLoader.js
<w> at resolve commonjs <PATH_REPLACED>/node_modules/.pnpm/@sentry+nextjs@7.61.0_next@13.4.12_react@18.2.0_webpack@5.88.2/node_modules/@sentry/nextjs/cjs/config/loaders/wrappingLoader.js
This started happening somewhere between Next 13.4.9 and 13.4.12 and @sentry/nextjs 7.57.0 and 7.61.0
Metadata
Metadata
Assignees
Labels
Package: nextjsIssues related to the Sentry Nextjs SDKIssues related to the Sentry Nextjs SDK
Projects
Status
No status