fix: Module '"node:readline"' has no default export.

[saadfrhan]

No description provided.

[codecov]

Codecov Report

Patch coverage: 100.00% and no project coverage change.

Comparison is base (e7c5bba) 72.33% compared to head (c580982) 72.33%.

Additional details and impacted files

@@           Coverage Diff           @@
##           master    #1276   +/-   ##
=======================================
  Coverage   72.33%   72.33%           
=======================================
  Files          42       42           
  Lines        4110     4110           
  Branches      669      669           
=======================================
  Hits         2973     2973           
  Misses        477      477           
  Partials      660      660           

Files Changed	Coverage Δ
packages/core/src/index.mts	80.35% <100.00%> (ø)

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[SBoudrias]

@saadfrhan where did you see this? Running under which environment? (and Node.js version?)

It's always been passing CI for Node 16, 18, and 20.

[saadfrhan]

GitHub Action link: https://github.com/saadfrhan/cli-nodejs-typescript-cli-template/actions/runs/5750427823/job/15587186738

Source code: https://github.com/saadfrhan/cli-nodejs-typescript-cli-template/tree/f3913f7989ae79a1522fd11cafdb54ca9d3f1747

I saw this error in the GitHub Action environment:

Node version: v16.20.1

[saadfrhan]

Tried with the latest LTS version as well, on the terminal.

[SBoudrias]

I think you need to add this line to your tsconfig:

{
  "compilerOptions": {
    "allowSyntheticDefaultImports": true
  }
}

To provide backwards compatibility, Node.js allows you to import most CommonJS packages with a default import. This flag tells TypeScript that it's okay to use import on CommonJS modules.

You could also consider bumping @type/node - that could be the problem too if very old.

I tried changing this on Inquirer's side to make it easier for users; but then it break elsewhere. So I don't think just the code change within Inquirer will fix it up everywhere in your own codebase. So unfortunately, this feel like a fix that must be applied on users' projects.