Qodana for JS
Qodana for JS is based on WebStorm. It provides static analysis for JavaScript or TypeScript projects.
Supported technologies
Qodana for JS provides inspections for the following technologies.
Programming languages | JavaScript TypeScript |
Markup languages | CSS HTML JSON and JSON5 RELAX NG XML YAML |
Scripting languages | Shell script |
Frameworks and libraries | Angular Cucumber EJS Handlebars/Mustache Less Node.js PostCSS Pug/Jade React Sass/SCSS Vue |
Supported features
The Qodana for JS linter provides the following Qodana features:
Feature | Available under licenses |
---|---|
Ultimate and Ultimate Plus | |
Ultimate and Ultimate Plus | |
Ultimate Plus | |
Ultimate and Ultimate Plus | |
Ultimate and Ultimate Plus | |
Ultimate Plus |
Try it now
Analyze a project locally
Install project dependencies
For a basic JavaScript project that has no external dependencies, no preliminary steps are required.
In case the project has external dependencies, you can set them up using the bootstrap
field in the qodana.yaml
file. For example, if your project dependencies are specified by the yarn.lock
file in your project root, add the following line to qodana.yaml
:
The command will be automatically executed before the analysis. You can use the npm
or yarn
commands to install dependencies.
Enable ESLint
ESLint is widely used in JavaScript projects. You can enable it using the qodana.yaml
file:
Run analysis
Qodana provides two options for local analysis of your code. Qodana CLI is the easiest option to start. Alternatively, you can use the Docker command from the tab.
Assuming that you have already installed Qodana CLI on your machine, you can run this command in the project root directory:
Here, the QODANA_TOKEN
variable refers to the project token.
To start, pull the image from Docker Hub (only necessary to get the latest version):
Start local analysis with source-directory
pointing to the root of your project and QODANA_TOKEN
referring to the project token:
Open http://localhost:8080
in your browser to examine inspection results. Here, you can also reconfigure the analysis, see the Inspection report section for details. When done, you can stop the web server by pressing Ctrl-C in the console.