How to include missing type definition files in typescript configuration?

Question

This is the same issue as How to allow modules that have missing .d.ts type definition?

VS Code stopped complaining after adding those files, but trying to compile using gulp sadly throw an error in the console.

(In fact today I noticed VS code stopped displaying most of the errors)

In ./src/dts/ I have:

dyo.d.ts

declare module 'dyo';

tsconfig.json

{
  "compilerOptions": {
    "lib": ["dom", "es2016", "es2017.object"],
    "rootDir": "src",
    "target": "es5",
    "outDir": "build",
    "moduleResolution": "node",
    //"noImplicitAny": false,
    "removeComments": true,
    "typeRoots": [
      "src/dts",
      "node_modules/@types"
    ]
  },
  "exclude": [
    "node_modules"
  ],
  "files": [
    "./src/dts/dyo.d.ts",
    "./src/dts/randomseed.d.ts"
  ]
}

The error:

error TS7016: Could not find a declaration file for module 'dyo'. '/mediatest/node_modules/dyo/dist/dyo.umd.js' implicitly has an 'any' type. Try npm install @types/dyo if it exists or add a new declaration (.d.ts) file containing declare module 'dyo';

I include the modules like so:

import { h, render } from 'dyo'

import * as _rng from 'random-seed'

The second module isn't working either.

The previous answer suggested to include files property and another question somewhere said to include the typeRoots property but both settings doesn't seem to be working.

Sorry for spamming SO about my typescript questions.

Jake Holzinger · Accepted Answer · 2019-01-19 01:26:23Z

2

I would suggest switching to types from typeRoots and using an include pattern rather than files.

{
  "compilerOptions": {
    "lib": ["dom", "es2016", "es2017.object"],
    "rootDir": "src",
    "target": "es5",
    "outDir": "build",
    "moduleResolution": "node",
    "removeComments": true,
    "types": [
      "node"
    ]
  },
  "include": [
    "**/*.ts"
  ]
}

I included the node type as well since you are using node module resolution, be sure to install @types/node if you have not already.

answered Jan 19, 2019 at 1:26

Jake Holzinger

6,0732 gold badges23 silver badges35 bronze badges

Sign up to request clarification or add additional context in comments.

3 Comments

HypeWolf Over a year ago

Thanks for your answer, I've installed @types/node and change the configuration, but I still get Try npm install @types/dyo` if it exists or add a new declaration (.d.ts) file containing `declare module 'dyo';`` :/

HypeWolf Over a year ago

I found the cause of it, gulp-typescript doesn't use tsconfig.json. I was able to change it's configuration to use the file. Finally. Thanks, it helped a lot.

ojathelonius Over a year ago

You can bypass this in TypeScript configuration by using noImplicitAny: false, see here : stackoverflow.com/a/65687243/6380030

Collectives™ on Stack Overflow

How to include missing type definition files in typescript configuration?

1 Answer 1

3 Comments

Your Answer

Linked

Hot Network Questions

Collectives™ on Stack Overflow

1 Answer 1

3 Comments

Your Answer

Sign up or log in

Post as a guest

Linked

Related