Closed

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?
Sentry Saas (sentry.io)
Which SDK are you using?
@sentry/nextjs
SDK Version
7.77.0
Framework Version
Next 14.0.1
Link to Sentry event
SDK Setup
client:
init({
dsn: SENTRY_DSN,
environment: process.env['ENVIRONMENT'],
tracesSampleRate: 0.1,
// 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.1,
// If the entire session is not sampled, use the below sample rate to sample
// sessions when an error occurs.
replaysOnErrorSampleRate: 1.0,
integrations: [new Replay()],
});
edge:
init({
dsn: SENTRY_DSN,
environment: process.env['ENVIRONMENT'],
tracesSampleRate: 0.1,
});
server:
init({
dsn: SENTRY_DSN,
environment: process.env['ENVIRONMENT'],
tracesSampleRate: 0.1,
});
Steps to Reproduce
I'm not sure. You can get the call stack from the sentry link attached.
node:internal/process/per_thread in process.memoryUsage at line 172:5
/var/task/node_modules/@sentry/node/cjs/integrations/context.js in Context._updateContext at line 76:41
/var/task/node_modules/@sentry/node/cjs/integrations/context.js in Context.addContext at line 56:33
After a bit of a research from my side, I see that the community uses 'graceful-fs'/'node-fs-extra' instead of 'fs' to prevent EM File errors.
Expected Result
No errors?
Actual Result
Throws this error.
Metadata
Metadata
Assignees
Type
Projects
Status
No status
Status
Waiting for: Community