Node SDK generating Error: ENOENT: no such file or directory

[Yareaj]

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/node

SDK Version

8.0.0.

Framework Version

Node v20.12.1

Link to Sentry event

https://ticket-tool-helper.sentry.io/issues/5357809318/?project=4507264120717312&query=is%3Aunresolved&referrer=issue-stream&stream_index=0

SDK Setup

import { init } from "@sentry/node";
import { nodeProfilingIntegration } from "@sentry/profiling-node";

init({
  dsn: process.env.SENTRY_DSN_URL,
  integrations: [
    nodeProfilingIntegration(),
  ],
  tracesSampleRate: 1.0,
  profilesSampleRate: 1.0
});

Steps to Reproduce

I'm using https://github.com/discordjs/discord.js and since I updated to Sentry v8, without changing any of my other dependencies, I'm facing the following error in a function that is simply trying to import a discord.js class.

[Error: ENOENT: no such file or directory, open 'C:\...\node_modules\@discordjs\builders\dist\@discordjs\formatters']

I think it's on sentry the root of the error given by the fact that when using @sentry/node@7.113.0 this error didn't happen. If I remove my sentry init, the program will work fine too

Expected Result

The program would not detect any error

Actual Result

A

[Error: ENOENT: no such file or directory, open 'C:\...\node_modules\@discordjs\builders\dist\@discordjs\formatters']

is captured as an error and stops the execution of the function that was doing an import

[FozzieHi]

I am also seeing this, but with a different library (although it is slightly related, as it depends on discord.js):

Error when loading '/app/dist/listeners/messageUpdate.js': [Error: ENOENT: no such file or directory, open '/app/node_modules/@sapphire/framework/dist/esm/@sapphire/result'] {
  errno: -2,
  code: 'ENOENT',
  syscall: 'open',
  path: '/app/node_modules/@sapphire/framework/dist/esm/@sapphire/result'
}

This is the Dockerfile I am using: https://github.com/FozzieHi/FormulaOne/blob/87c9bdb9deb02ca6cc97f8ed3d1883f0e4be2716/Dockerfile

I've checked the path, node_modules/@sapphire/framework/dist/esm/@sapphire and it doesn't exist on v8 or the app running v7 either, so I think that this is v8 somehow changing the import path? I haven't dug into it further yet to see if it's caused by the sentry update itself, or the packages it brings with it. I also haven't checked if it's possibly related to source maps as that's the only other thing I can think of.

[FozzieHi]

I've tried disabling source maps but that hasn't fixed it.

I've taken a look at the directories again:

• Doesn't exist: node_modules/@sapphire/framework/dist/esm/@sapphire/result
• Does exist: node_modules/@sapphire/result/dist/esm

I'm not sure if it is somehow renaming the imports for these or not?

[chentsulin]

It might be caused by a bug in import-in-the-middle:

• no such file or directory nodejs/import-in-the-middle#59
• Imports from @react-email/components break with import-in-the-middle nodejs/import-in-the-middle#62
• Fails to resolve exports defined submodule when reexported by another package nodejs/import-in-the-middle#63

[rnenjoy]

Error: ENOENT: no such file or directory, open '/srv/http/dev-net23/backend/node_modules/.pnpm/puppeteer@22.9.0/node_modules/puppeteer/lib/esm/puppeteer/puppeteer-core/internal/puppeteer-core.js'
    at async open (node:internal/fs/promises:641:25)
    at async readFile (node:internal/fs/promises:1254:14)
    at async getSource (node:internal/modules/esm/load:42:14)
    at async defaultLoad (node:internal/modules/esm/load:127:34)
    at async nextLoad (node:internal/modules/esm/hooks:791:22)
    at async getExports (/srv/http/dev-net23/backend/node_modules/.pnpm/import-in-the-middle@1.7.4/node_modules/import-in-the-middle/lib/get-exports.js:63:21)
    at async processModule (/srv/http/dev-net23/backend/node_modules/.pnpm/import-in-the-middle@1.7.4/node_modules/import-in-the-middle/hook.js:134:23)
    at async processModule (/srv/http/dev-net23/backend/node_modules/.pnpm/import-in-the-middle@1.7.4/node_modules/import-in-the-middle/hook.js:160:20)
    at async getSource (/srv/http/dev-net23/backend/node_modules/.pnpm/import-in-the-middle@1.7.4/node_modules/import-in-the-middle/hook.js:269:60)
    at async load (/srv/http/dev-net23/backend/node_modules/.pnpm/import-in-the-middle@1.7.4/node_modules/import-in-the-middle/hook.js:335:26) {
    ```

Seems to be import-in-the-middle

[net-tech]

Was experiencing this too. We use a mono repo for our product and the issue also occurs in those.

Very annoying that this was not caught before the v8 release to be honest. It caused a 1h 30min downtime on a service for us in a Docker environment and took some investigation to figure out.