Turbopack: Ignore realpath errors during module resolution, matching node's behavior (#99951)
Addresses agent feedback: https://vercel.slack.com/archives/C0ANB536V62/p1791479564863939 Certain setups could cause us to report a Turbopack internal error due to this bail. In testing, it appears that node treats realpath errors (e.g. due to a symlink cycle) the same as not-found. So while these errors could be useful, we shouldn't emit them. I discussed this with @lukesandberg, and because the resolution algorithm is so hot, emitting issues here (e.g. warnings) could be extremely noisy. So it seems better not to do that. If somebody's `node_modules` is severely f*ked up, `MissingNextFolderIssue` should already provide a sufficiently good error message: https://github.com/vercel/next.js/blob/3fd5b1c0b23546e1256f37ee7d705e255a4938e2/crates/next-core/src/next_import_map.rs#L1320-L1323
Showing
Please
register
or
sign in
to comment