Skip to content
This repository has been archived by the owner on Jul 12, 2024. It is now read-only.

Typing broken #11

Open
CookieKat opened this issue Oct 30, 2023 · 0 comments
Open

Typing broken #11

CookieKat opened this issue Oct 30, 2023 · 0 comments

Comments

@CookieKat
Copy link

CookieKat commented Oct 30, 2023

Hey,

first a short recap, since mine got lost in the uber space: For me the typing with 4.0 is broken. All types, at least in core, come as any.
My typescript is up to date and my project is esm, too.
My tsconfig compiler options:

"compilerOptions": {
    "target": "esnext",
    "outDir": "dist",
    "module": "NodeNext",
    "sourceMap": true,
    "declaration": true,
    "strict": true,
    "newLine": "lf",
    "lib": ["esnext"],
    "types": ["node", "vitest/globals"],
    "skipLibCheck": true,
    "allowUnreachableCode": false,
    "allowUnusedLabels": false,
    "forceConsistentCasingInFileNames": true,
    "noEmitOnError": true,
    "noFallthroughCasesInSwitch": true,
    "noImplicitReturns": true,
    "pretty": true
  },

Maybe the "module": "NodeNext" brakes it together with one thing I noticed in your code base, your relative paths in imports have no .js endings. With the ending it's module resultion save, see here

I'd like try fixing it myself but it seems there is a secret to get it up and running... Did I missed a ReadMe or something?

Thanks :)

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant