fix: use debugger for package resolution warnings

[antfu]

Reverts #4822

I think the original behavior (trying to get submodule paths) is expected.

The log creates too much noise that ppl usually don't need to care about. For the debugging purpose stated in #4822, I think it's better to modify local node_modules when debugging.

[haoqunjiang]

Or, we can use a debug log here?

[benmccann]

When I've seen this print it's due to a Vite bug: #4425. I think the best solution here would be to fix that bug rather than silently drop the exception. It is causing real issues in my applications, so it's helpful to know it's happening. But if we need to silence it in the meantime I agree that debug would be better

[patak-dev]

+1 to show this with a debug log, there is also a missing break that would make the logs easier to read.

Maybe we could use a warn once with a single short message if not debugging so people know that they may need to dig deeper. "Some packages may have incorrect...." and a pointer to use debug logs to see more

[antfu]

Updated using debugger. Since it scans all the devDependencies, which could include many packages that are not intended to use that way (in the screenshots, @types/* and cli tools for example). I don't think we should throw any message regarding the scanning failures by default here, as it might have many false positives and make users nervous.

A better solution I would think about this is that we record that error silently, and we the import analyzer actually scanned the usages with that package, and then we could warn about that there might be something wrong. For example,

{
  "devDependencies": {
     // here we assume both packages have something wrong with their exports
	 "@types/node": "*",
     "lodash": "*"
  }
}

// some-module.js
import set from 'lodash/set'

Warning when scanned some-module.js:

Trying to importing lodash/set in some-module.js but lodash does not export the module or there is something wrong during the package resolving, externalization skipped. \n {{error}}