The `sentry.server.config.js` is cached?

[morgs32]

• Review the documentation: https://docs.sentry.io/
• Search for existing issues: https://github.com/getsentry/sentry-javascript/issues
• Use the latest release: https://github.com/getsentry/sentry-javascript/releases
• Provide a link to the affected event from your Sentry account

Package + Version

• @sentry/browser
• @sentry/node
• raven-js
• raven-node (raven for node)
• other: @sentry/nextjs

Version:

6.16.1

Description

At some point, this file sentry.server.config.js seems to be caches, perhaps by webpack, and I cannot manage to uncache it. Adding simple logs or throwing errors from this file does nothing.

Any ideas?

[morgs32]

I should add, I have tried:

• downgrading to next 11
• setting cache: false on the webpack confi via next.config.js

[morgs32]

Here is a relatively simple nextjs app: https://github.com/morgs32/morganatwork that should reproduce the issue.
I suspect that if you:

• clone it and run it
• and put your own DSN here on line 14,
• you will see "SENTRY_DSN" logged on line 9
• when hitting the api at http://localhost:3333/api/hello.
• Kill the process
• Then uncomment the error on on line 11,
• Run yarn dev again
• hit the api again
• And you WON'T see the error OR the log
• Uncomment the error
• And you'll STILL never see the log (SENTRY_DSN) again

[lobsterkatie]

Hi, @morgs32.

It's not clear to me from the repro steps you outlined if you're rebuilding your app after you change sentry.server.config.js. Are you? If not, can you please try doing that and see if you still have a problem?

(Rebuilding is necessary because the contents of the file are injected into your app during build.)