default export usage with NodeNext? | TypeScript Community | Page 1

lyric pulsar Jan 19, 2023, 12:30 PM

#

I have my moduleResolution set to NodeNext, and I'm importing an ESM package:

declare const got: import("./types").Got;
export default got;

import got from "got";

Now I think got should be the default export with type Got, but it's not. Typescript tells me it only has a property named default. So I can do got.default.post() but I can't do got.post(). What am I doing wrong here? Why do I have to explicitly specify .default in my code when what I'm doing is importing a default export?

I shall note that (got as any).post() works just fine at runtime, so it seems to be a typescript bug. I'm using Typescript 4.8.4.

upper sand Jan 19, 2023, 2:19 PM

#

can you share your tsconfig?

lyric pulsar Jan 20, 2023, 1:52 PM

#

sorry I missed the message somehow... here's the config:

{
  "extends": "./node_modules/@itwin/build-tools/tsconfig-base.json",
  "compilerOptions": {
    "alwaysStrict": true,
    "esModuleInterop": false,
    "experimentalDecorators": true,
    "forceConsistentCasingInFileNames": true,
    "incremental": true,
    "inlineSources": true,
    "jsx": "react",
    "noFallthroughCasesInSwitch": false,
    "noImplicitAny": true,
    "noImplicitOverride": true,
    "noImplicitReturns": true,
    "noImplicitThis": true,
    "noUnusedLocals": false,
    "noUnusedParameters": true,
    "skipLibCheck": true,
    "sourceMap": true,
    "strict": true,
    "strictNullChecks": true,
    "stripInternal": false,
    "target": "ES2019"
    "declaration": false,
    "declarationMap": false,
    "tsBuildInfoFile": "./lib/tsconfig.tsbuildinfo",
    "outDir": "./lib",
    "module": "NodeNext",
    "moduleResolution": "NodeNext",
    "types": ["mocha", "node"],
    "allowSyntheticDefaultImports": true
  },
  "include": [
    "./src/**/*.ts*"
  ]
}

upper sand Jan 20, 2023, 2:00 PM

#

i suspect you don't want allowSyntheticDefaultImports enabled (see https://www.typescriptlang.org/tsconfig#allowSyntheticDefaultImports)

lyric pulsar Jan 20, 2023, 6:21 PM

#

🤔 thanks, I don't remember why that's there but I'll try to make my code work without it

lyric pulsar Jan 23, 2023, 12:26 PM

#

upper sand i suspect you don't want `allowSyntheticDefaultImports` enabled (see <https://ww...

so changing it to false didn't change anything

lyric pulsar Jan 23, 2023, 1:31 PM

#

for now I'm using this workaround:

import gotImport, { ... } from "got";
const got = gotImport.default;

vernal trellis Jan 23, 2023, 2:57 PM

#

lyric pulsar for now I'm using this workaround: ```ts import gotImport, { ... } from "got"; c...

if u dont need to import it u can export it in one line

export {default as got, otherStuff...} from 'got';

lyric pulsar Jan 23, 2023, 3:01 PM

#

vernal trellis if u dont need to import it u can export it in one line ```js export {default as...

what do you mean I don't need to import it?

#

got is an npm package, I can't modify it

#

I just want to import it, I don't want to re-export

#default export usage with NodeNext?