[BUG]: @sentry/profiler-node

[JesseKoldewijn]

Link to the code that reproduces this issue

https://github.com/JesseKoldewijn/JKinsight

To Reproduce

1. clone repo
2. remove Next.js config entry of experimental external package
3. try to run either dev or build command and see sentry crash due to internal error within bundling process of the @sentry/profiling-node package

Current vs. Expected behavior

current: dev and build cant be run without manually adding external package entry in experimental Next.js config

expected: package can be used without crashing inside bundling process

Verify canary release

• I verified that the issue exists in the latest Next.js canary release

Provide environment information

Operating System:
  Platform: linux
  Arch: x64
  Version: #1 SMP Mon Nov 6 23:32:38 UTC 2023
Binaries:
  Node: 18.17.1
  npm: 10.2.5
  Yarn: 1.22.21
  pnpm: 8.14.1
Relevant Packages:
  next: 14.1.1-canary.0
  eslint-config-next: 14.0.4
  react: 18.2.0
  react-dom: 18.2.0
  typescript: 5.3.3
Next.js Config:
  output: N/A

Which area(s) are affected? (Select all that apply)

SWC transpilation

Which stage(s) are affected? (Select all that apply)

next dev (local), next build (local)

Additional context

No response

[JesseKoldewijn]

@balazsorban44 hey man sorry for the ping, just wanted to give ya a heads-up that I'm creating a fix for this issue right away in the form of a PR. Beside the issue, hope ya had a great new year's as wel btw! 😄

[github-actions]

This closed issue has been automatically locked because it had no new activity for 2 weeks. If you are running into a similar issue, please create a new issue with the steps to reproduce. Thank you.