Skip to content

typescript: defined tsconfig.json paths not consistent with reality #158

@nrdxp

Description

@nrdxp

I have a wip package effort going on here:
https://github.com/input-output-hk/cardano-js-sdk/tree/dn2-wip

After working out several other issues during the build, I've reached a point where I keep getting strange type errors during the typescript compiler run. After digging into the node_modules folder, and looking through the various tsconfig.json of various dependencies, I've noticed that they have various path definitions point to non existent locations (inside the source derivation), meaning the compiler cannot find all the type definitions, meaning ultimately that the build fails.

To reproduce one of the errors I'm seeing run: nix build .\#@cardano-sdk/core -L from that branch I linked above.

As a concrete example of a bad path, you can enter the failed build's source derivation and cd into node_modules/@bcoe/v8-coverage/tsconfig.json and see it has the following defintion:

    "typeRoots": [
      "src/lib/custom-typings",
      "node_modules/@types"
    ]

But it's local node_modules folder is completely empty

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't workingnodejs

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions