Default imports don't work with module resolution node16

[sharifzadesina]

🔎 Search Terms

"Default imports don't work with module resolution node16", "node16", "default imports"

🕗 Version & Regression Information

• This is the behavior in every version I tried, and I reviewed the FAQ for entries about it

⏯ Playground Link

https://stackblitz.com/edit/stackblitz-starters-bakzhy

Node.js: Run using node src/index.js
Typescript: run using npx tsc and see the error!

💻 Code

import pino from "pino";

const prettyTransport = {
  target: 'pino-pretty',
  level: 'debug',
  options: {
    translateTime: 'HH:MM:ss Z',
    ignore: 'pid,hostname',
  },
};

const p = pino({
  transport: {
    targets: [prettyTransport]
  },
  level: 'debug'
})

p.debug('test');

🙁 Actual behavior

This expression is not callable.
  Type 'typeof import("/home/sina/Projects/test/node_modules/pino/pino")' has no call signatures.

🙂 Expected behavior

It works in Node (tested with v18 and v20), why does typescript show the error?!

Just run the code above in NodeJS, we have no double default issue and everything works as expected.

Additional information about the issue

This is related to #53349 and #50058#issuecomment-1404411380.

[jakebailey]

This package is incorrectly typed: https://arethetypeswrong.github.io/?p=pino%409.2.0

[sharifzadesina]

@jakebailey Can you elaborate a bit more?! Isn't node16 supposed to copy NodeJS behavior?! Also, we are not supposed to use node16 then?! because it is not NodeJS behavior.

[sharifzadesina]

We have the same issue for ioredis package.

But the interesting thing is, according to this, the ioredis package doesn't have invalid types.

Playground:

https://stackblitz.com/edit/stackblitz-starters-bakzhy

Node.js: Run using node src/ioredis.js
Typescript: run using npx tsc and see the error!

[sharifzadesina]

Just investigating further:

In ioredis, even when I comment module.exports =, the error won't be gone.

As you see, we now have only module.exports.default and export default.

[fatcerberus]

node16 does match Node runtime behavior for your code, the problem here is that the types for the package you’re importing (its .d.ts files) are telling TS the wrong thing about how its exports are structured. In other words the problem is on the package author’s end.

[sharifzadesina]

Found the cause of the problem. closing.