I stumbled upon this issue as well. The only solution I found was add the skipLibCheck option and set it to true in the compilerOptions of my tsconfig.json: { “compilerOptions”: { “skipLibCheck”: true } } According to the doc, it will skip type checking of all declaration files (*.d.ts), which were the ones throwing the … Read more
Full example if anyone needs it: { “compilerOptions”: { … }, “include”: [ “src/**/*” ], “exclude”: [ “src/**/*.spec.ts” ] }
This is possible, and it turns out, not hard. The reason the solution is not obvious is because typescript relies on the rootDir to decide the directory structure of the output (see this comment from Typescript’s bossman), and only code included in the output or in package dependencies can be imported. If you set rootDir … Read more
One of the ways to get rid of that error is by modifying d.ts file as follows: declare module “*.png” remove { const value: string; export default value; } or alternatively you can do: declare module “*.png” { const value: any; export default value; } Update The best solution with type-checking is: declare module “*.png” … Read more
I faced the same issue. I tried many things and now i got a solution which works for me. I have an app and a library in my angular project. I want to use a library alias in my app. I have following structure: ├── projects │ └── lib │ └── src │ └── lib … Read more
You need to set the configuration through the TS_NODE_COMPILER_OPTIONS environment variable Example code on an unix machine: TS_NODE_COMPILER_OPTIONS='{“module”:”commonjs”}’ \ mocha –require ts-node/register ‘test/**/*.spec.{ts,tsx}’ Explanation extracted from the repository documentation CLI and Programmatic Options Environment variable denoted in parentheses. -T, –transpile-only Use TypeScript’s faster transpileModule (TS_NODE_TRANSPILE_ONLY, default: false) -I, –ignore [pattern] Override the path patterns to … Read more
This is because VSCode’s Typescript version is not using the newest babel features that create-react-app uses by default. You can change VS Code to use the workspace’s version of Typescript instead, which will fix this issue. Open a TypeScript or JavaScript file and click on the TypeScript version number in the Status Bar. A message … Read more
I have no idea why this is now working on the eleventh time I tried (yet didn’t the first 10), but the /* seems to be the secret sauce, and the example in the docs is apparently pointing to a specific file (and the file extension is omitted). { “compilerOptions”: { “baseUrl”: “./src”, // setting … Read more
These days it is much easier as vscode has better support for this. You can use this directory structure so all the code is independent: ├── frontend/ │ ├── src/ │ │ ├── <frontend code> │ ├── package.json │ ├── tsconfig.json ├── shared/ │ ├── package.json ├── backend/ │ ├── src/ │ │ ├── <backend … Read more
I ended up defining multiple config files and use extends to simplify them. Say I have two files: tsconfig.json and tsconfig.build.json // tsconfig.json { … “exclude”: […] } // tsconfig.build.json { … “files”: [ “typings/index.d.ts”, “src/index.ts” ] } This way, I can have fine control on what to build (using tsc -p tsconfig.build.json) and what … Read more