I was having a similar problem, but I could not add –files, because I run ts-node by registering the module through mocha (i.e. mocha -r ts-node/register …). I could solve it by adding a files and a ts-node section to tsconfig.json like this: // tsconfig.json { “ts-node”: { “files”: true }, “files”: [ “src/index.ts”, “src/global.d.ts” … Read more
Had the same issue. Just add this “resolutions”: { “@types/react”: “17.0.2”, “@types/react-dom”: “17.0.2” }, to package.json file and run yarn command. UPD: Just a bit detailed answer: @types/react-dom has its own dependencies and one of them is @types/react with a version set to ‘*’ – a major release, that now, probably, refers to 18. Even … Read more
No, this is not possible in TypeScript as of TS4.1. There are two issues I see; one might be overcome with a change to the TypeScript standard library typings for Array.prototype.map(), but the other would require a fairly large change to the type system to work in general and cannot currently be handled in a … Read more
If you need to overwrite an existing property declaration to change the type, you’ll need to fork the @types/expo types. The easiest way is probably to copy the index.d.ts file into your typings directory and uninstall the original @types/expo package. Or you can use a tool such as Braid (disclosure: I am a Braid contributor) … Read more
You are right – declaration:true implies that only for each given .ts file tsc generates and copies a corresponding .d.ts output file to the build directory (in addition to .js and .map if applicable). So tsc will not copy your custom types.d.ts file to the output directory. Basically .d.ts files are seen as untouchable input … Read more
As of TypeScript 2.0, typings is no longer required. The npm organization is an entity to setup a developers team. I believe Microsoft setup the @types organization in npm and added the TypeScript developer team to the organization. Packages on under the @types organization are published automatically from DefinitelyTyped using the types-publisher tool as per … Read more
As of TypeScript 2.* the ‘tsconfig.json’ has the following two properties available: { ‘typeRoots’: [], ‘types’: [] } I’ll detail both in order. ‘typeRoots’ specifies root folders in which the transpiler should look for type definitions (eg: ‘node_modules’). If you’ve been using typescript, you know that for different libraries that have not been written using … Read more
Create node_modules folder under your src, then put typings of module(s) you want to overwrite inside: ├── node_modules │ └── … │ └── src ├── index.ts ├── … your codes … │ └── node_modules └── <module-to-be-overwritten> └── index.d.ts No need to modify compilerOptions in tsconfig.json. Read How TypeScript resolves modules section in https://www.typescriptlang.org/docs/handbook/module-resolution.html.
Unfortunately these things are not currently very well documented, but even if you were able to get it working, let’s go over your configuration so that you understand what each part is doing and how it relates to how typescript processes and loads typings. First let’s go over the error you are receiving: error TS2688: … Read more
“Magically available interfaces” or global types is highly discouraged and should mostly be left to legacy. Also, you should not be using ambient declaration files (e.g. d.ts files) for code that you are writing. These are meant to stand-in the place of external non-typescript code (essentially filling in the typescript types into js code so … Read more