Module not found for TypeScript 4.7

Expected Behaviour

Able to bundle.

Actual Behaviour

errors such as:

Module not found: Error: Can't resolve './tersible.js'

Steps to Reproduce the Problem

In TypeScript 4.7, the NodeNext module resolution requires the source code to specify the extension as .js. e.g.:

// index.ts
export * from './tersible.js' // for `tersible.ts`

For ts-jest on the jest side, it solves that by doing a transformation:

  moduleNameMapper: {
    '^(\\.{1,2}/.*)\\.js$': '$1',
  },

Maybe something similar is needed? Would be great to add a section in the readme specifically for that.

Location of a Minimal Repository that Demonstrates the Issue.

Not a minimal repo, but here is an example: https://github.com/unional/tersify. Run yarn bundle in the repo

🌷

[alexander-akait]

hm, why don’t use https://webpack.js.org/configuration/resolve/#resolveextensionalias? I think it will work

[unional]

https://github.com/justland/just-web/pull/58

One update. After I add the cjs/package.json workaround, at least the CommonJS side resolution is working fine. It’s not directly related to this issue, but it shows that having due-export (CJS + ESM/NodeNext) able to work at the end application.