In more complex projects, you may have more than one jsconfig.json file defined inside a workspace. Place the file at the root of your JavaScript code as shown below. We define this part of our code, the client side of our website, as a JavaScript project by creating a jsconfig.json file. For this reason, we offer a hint to create a jsconfig.json file when you open a JavaScript file in a fresh workspace. The JavaScript experience is improved when you have a jsconfig.json file in your workspace that defines the project context. The file itself can optionally list the files belonging to the project, the files to be excluded from the project, as well as compiler options (see below).

The presence of such a file in a directory indicates that the directory is the root of a JavaScript project. As long as a file a.js doesn't reference a file b.ts explicitly (either using import or CommonJS modules), there is no common project context between the two files.Įxplicit Project - with jsconfig.json: A JavaScript project is defined via a jsconfig.json file. Visual Studio Code's JavaScript support can run in two different modes:įile Scope - no jsconfig.json: In this mode, JavaScript files opened in Visual Studio Code are treated as independent units. jsconfig.json is tsconfig.json with 'allowJs' attribute set to true. Tip: jsconfig.json is a descendant of tsconfig.json, which is a configuration file for TypeScript. Tip: If you are not using JavaScript, you do not need to worry about jsconfig.json. The jsconfig.json file specifies the root files and the options for the features provided by the JavaScript language service. The presence of jsconfig.json file in a directory indicates that the directory is the root of a JavaScript Project. Configure IntelliSense for cross-compilingĮdit jsconfig.json What is jsconfig.json?.

Es6 includes