nuxt: Nitro externalized package has incorrect main entry point

I am seeing this issue still with rc12. The below error is generated for multiple packages:

 WARN  Multiple major versions of package parse5 are being externalized. Picking latest version:                                                        14:37:18

  - /xxx/node_modules/parse5@5.1.1
  + /xxx/node_modules/parse5-htmlparser2-tree-adapter/node_modules/parse5@6.0.1

Then at nuxi preview:

Nuxi 3.0.0-rc.12                                                                                                                                        14:37:23
ℹ Node.js version: 18.10.0                                                                                                                              14:37:23
ℹ Preset: node-server                                                                                                                                   14:37:23
ℹ Working dir: .output                                                                                                                                  14:37:23
ℹ Loading .env. This will not be loaded when running the server in production.                                                                          14:37:23
ℹ Starting preview command: node ./server/index.mjs                                                                                                     14:37:23
                                                                                                                                                        14:37:23
node:internal/modules/cjs/loader:393
      const err = new Error(
                  ^

Error: Cannot find module '/xxx/.output/server/node_modules/parse5/lib/index.js'. Please verify that the package.json has a valid "main" entry
    at tryPackage (node:internal/modules/cjs/loader:393:19)
    at Module._findPath (node:internal/modules/cjs/loader:606:18)
    at Module._resolveFilename (node:internal/modules/cjs/loader:971:27)
    at Module._load (node:internal/modules/cjs/loader:833:27)
    at Module.require (node:internal/modules/cjs/loader:1051:19)
    at require (node:internal/modules/cjs/helpers:103:18)
    at Object.<anonymous> (/xxx/.output/server/node_modules/cli-highlight/dist/index.js:30:27)
    at Module._compile (node:internal/modules/cjs/loader:1149:14)
    at Module._extensions..js (node:internal/modules/cjs/loader:1203:10)
    at Module.load (node:internal/modules/cjs/loader:1027:32) {
  code: 'MODULE_NOT_FOUND',
  path: '/xxx/.output/server/node_modules/parse5/package.json',
  requestPath: 'parse5'
}

Node.js v18.10.0

 ERROR  Command failed with exit code 1: node ./server/index.mjs                                                                                        14:37:23

  at makeError (node_modules/nuxi/dist/shared/nuxi.bc8d057a.mjs:619:11)
  at handlePromise (node_modules/nuxi/dist/shared/nuxi.bc8d057a.mjs:1026:26)
  at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
  at async Object.invoke (node_modules/nuxi/dist/chunks/preview.mjs:63:5)
  at async _main (node_modules/nuxi/dist/cli.mjs:50:20)

npm ls parse5:

xxx @ /xxx
└─┬ typeorm@0.3.10
  └─┬ cli-highlight@2.1.11
    ├─┬ parse5-htmlparser2-tree-adapter@6.0.1
    │ └── parse5@6.0.1
    └── parse5@5.1.1

Same happens for packages pako, uuid, readable-stream, @xmldom/xmldom and tslib. Possibly these changed their module formats between major versions, and that is throwing the compiler off?

@danielroe Hey, It seems like the issue isn’t resolved (RC 11). This time the semver.js isn’t generated. I’ve updated my reproduction.

Same issue here with: https://www.npmjs.com/package/jose

[nuxt] [request error] [unhandled] [500] Cannot find module '/path/to/project/.output/server/node_modules/jose/dist/node/cjs/index.js'
  at createEsmNotFoundErr (node:internal/modules/cjs/loader:983:15)  
  at finalizeEsmResolution (node:internal/modules/cjs/loader:976:15)  
  at resolveExports (node:internal/modules/cjs/loader:493:14)  
  at Function.Module._findPath (node:internal/modules/cjs/loader:533:31)  
  at Function.Module._resolveFilename (node:internal/modules/cjs/loader:942:27)  
  at Function.Module._load (node:internal/modules/cjs/loader:804:27)  
  at Module.require (node:internal/modules/cjs/loader:1028:19)  
  at require (node:internal/modules/cjs/helpers:102:18)  
  at Object.<anonymous> (./server/node_modules/jwks-rsa/src/utils.js:1:14)  
  at Module._compile (node:internal/modules/cjs/loader:1126:14)

Server compilation generates /path/to/project/.output/server/node_modules/jose/dist/node/esm/index.js

This happens for me with a few packages, semver, lru-cache, jws, yallist and jwa.

I understand the issue is not related to specific packages, but I wanted to post them here anyway for other people that encounter the same issue. I’m using the edge release (currently 3.0.0-rc.13-27781436.1f6b3be).

This should be resolved in the edge channel, or in the next RC.

Let me know if not and I’ll reopen.

Even after this fix, overriding an older version can provoke error in case of using another module that depends on overrided version, so forcing newer version can lead to incompatibility problems (googleapis and jsonwebtoken use jwa with different versions for example) maybe adding an option to disable trace for nested modules would be temporarily a solution

This is fixed in 3.1. https://github.com/unjs/nitro/pull/782