typescript - cannot find parent tsconfig.json

can't recreate using the same config and project structure... Can you reproduce the issue in a new project? Also, do you have any symlinks/junctions in the project path?

Will try with a new project. No, I don't use symlinks.

I also have the same info message. I have just moved to webstorm from VS Code. I have no issues, but this warning now appears, so it must be an IDE related issue.

Also, typescript is now not finding basic Jest types, maybe some mismatched typescript and ide config?

TypeScript compiler service uses the nearest tsconfig.*.json current file is included in for compiling your files. The message 

Cannot find parent 'tsconfig.json'

indicates that no tsconfig.*.json files current file is included in are found.

How many tsconfig.*.json files do you have in your project, what do they look like? Is the error reported for all .ts files, or for some certain ones only?

Same here. WS version 2018.2.1. Cannot find this tsconfig.

Try adding `tsconfig.webpack.json` to the list of Typescript Config file type patterns in Settings | Editor | File Types

I was previously seeing this message, however it is not appearing anymore, and the Jest types are being resolved. Here is my working tsconfig file.

Not sure if this will help, I cant say exactly what caused the message to stop showing up, we made a number of changes to the tsconfig file.

{
    "compilerOptions": {
        "moduleResolution": "node",
        "target": "es5",
        "noImplicitAny": true,
        "sourceMap": true,
        "outDir": "dist",
        "baseUrl": ".",
        "rootDir": ".",
        "paths": {
            "*": ["node_modules/*", "src/types/*"]
        },
        "lib": ["es2016", "dom", "esnext.asynciterable", "es2017.object"]
    },
    "include": ["src/**/*"],
    "exclude": ["node_modules", "**/*.spec.ts", "dist"]
}

I was having the same problem here. I have a monorepo project where the "Cannot find parent 'tsconfig.json' " message was showing up.

I've managed to mitigate this error by setting '--project "<path totsconfig.json>" ' in the options field at "Languages & frameworks > Typescript". It shouldn't be necessary to set it this way thought. 

Same problem with the newest Idea 2018.3 - I had to add `--project typescript/tsconfig.json` in the options for a monorepo, where the typerscript code is in /typescript/

can you share a sample project that can be used to recreate the issue?

Create a project where `tsconfig.json` is inside a folder /foo

Create a file /foo/bar.ts with content `const a = async function(){};`

Typescript compiler will complain about Promise lib missing, even if  you have listed `es2015` in libs. 

here you are:

as you can ssee, no problems are reported, and no warnings about not found config are there

I honestly dont know - I removed the --project typescript/tsconfig.json and now it works even without it, but yesterday it didnt.

Maybe just add an option to see which is the effective typescript/tsconfig.json and allow the user to select an alternative one - this should do it! 

Please vote for https://youtrack.jetbrains.com/issue/WEB-18963;

Normally it's a config nearest to current file: WebStorm follows the compiler logic here - it uses the nearest tsconfig.json current file is included in for compiling, traversing the folders hierarchy from current folder up to the IDE project root. 

I had the same problem, the problems started when I renamed both the folder and project name. I trashed the .idea folder, restarted the ide and it fixed the issue.

I too am having this issue.

i have a monorepo with yarn workspaces.  so there are a handful of tsconfig files.

in one space:

tsconfig.json

/modules/account/account.entity.ts

^ the account.entity.ts was complaining that is could not fine the tsconfig.json

when I moved it up a level to /modules/tsconfig.json

it worked  BUT -- i rather not have that there

Please see above - the IDE uses the nearest tsconfig.json current file is included in (check "include": [], "files": [], etc.), traversing the folders hierarchy from current folder up to the IDE project root. Sibling folders are not processed

That did it -- there was something funky in my "include": []  

Thanks!!!

I had the same issue, fixed with using the `--project` option.