[RClaudiuM]

Fixes #621

What

A require() call inside an ES module (through module.createRequire, or the global require with mixedModules) was resolved with the import condition. emitDependency resolved every specifier in deps with cjsResolve = !isESM, and in an ES module deps held both the static import/export ... from declarations and the require() calls. For a dual package whose exports subpath has separate import and require targets, nft traced the ESM build while Node loads the CommonJS one, so the deployed function fails with MODULE_NOT_FOUND.

Fix

• analyze now adds static import and export ... from sources to imports, next to dynamic import() (and module.register), which are already resolved with the import condition.
• deps now only holds require-like references (require(), createRequire, require.resolve, special cases, wildcard requires), so emitDependency always resolves it with the require condition.

Relative and absolute paths resolve the same way under both conditions, so this only changes bare and # specifiers reached through require() in an ES module.

Tests

New unit fixture esm-require-exports-conditions: an ES module imports dual/imported and requires dual/required through createRequire. Each subpath has separate import and require targets.

• Before: traces esm/imported.js and esm/required.js (the test fails).
• After: traces esm/imported.js and cjs/required.js.

The repro from the issue (createRequire + require("dual/sub")), with mixedModules both true and false:

before: node_modules/dual/esm/sub.js node_modules/dual/package.json
after:  node_modules/dual/cjs/sub.js node_modules/dual/package.json

pnpm prettier-check, pnpm build and pnpm test pass locally. The exceptions are the bcrypt, ffmpeg-static and leveldown integration tests: they fail the same way on main here because I installed without running native build scripts.