JavaScript

The analyzer is backwards compatible with ESLint, and will respect the ESLint config files present in your project.

​

Configuration - .deepsource.toml

This section covers configuration specific to the javascript analyzer. Please make sure to read the general configuration guide first.

​

name

• Type: String
• Presence: mandatory
• Description: Shortcode of the analyzer.
• Example:

​

enabled

• Type: Boolean
• Presence: optional
• Description: Toggle whether this analyzer should be run.
• Example:

​

meta

• Type: Table
• Presence: optional
• Description: Any supported metadata to pass to the analyzer.
• Example:

​

plugins

• Type: Array
• Presence: optional
• Description: The JavaScript Frameworks being used in the project. Currently, we support React,Vue, EmberJS, Meteor, Angular and AngularJS.
• Available Values: react, vue, ember, meteor, angular and angularjs
• Default Value: None
• Example:

​

dependency_file_paths

• Type: Array
• Presence: optional
• Description: A list of paths having files (e.g. package.json or tsconfig.json) relative to the repository’s root that specify external dependencies. The analyzer uses this to report dependency metrics and improve analysis accuracy.
• Example:

​

environment

• Type: Array

• Presence: optional

• Description: The global variables related to the environments used that need to be predefined for the project.

• Available Values: nodejs, browser, jest, mocha, jasmine, jquery, mongo, cypress, vitest

  • nodejs - Adds Node.js global variables and Node.js scoping
  • browser - Adds Browser specific global variables
  • jest - Adds Jest global variables
  • mocha - Adds Mocha testing global variables
  • jasmine - Adds Jasmine testing global variables for version 1.3 and 2.0
  • jquery - Adds jQuery global variables
  • mongo - Adds MongoDB global variables
  • cypress - Adds Cypress global variables
  • vitest - Adds Vitest global variables

• Default Values: [“nodejs”, “browser”]

• Example:

​

globals

• Type: Array
• Presence: optional
• Description: The list of global variables that are used in the project. Helps the analyzer recognize global variables and not report them as undefined.
• Example:

​

module_system

• Type: String

• Presence: optional

• Description: The type of modules used in the project.

• Available Values: commonjs, es-modules and amd

  • commonjs - The CommonJS Module System. (require / exports)
  • es-modules - ES Modules (import / export)
  • amd - Asynchronous Module Definition (define / require)

• Default Value: “es-modules”

• Example:

​

dialect

• Type: String
• Presence: optional
• Description: The dialect of JavaScript used in the project. Currently, we support TypeScript and Flow.
• Available Value: typescript and flow
• Default Value: “typescript”
• Example:

​

skip_doc_coverage

• Type: Array

• Presence: optional

• Description: Specify which artifacts to skip when detecting documentation issues and calculating documentation coverage.

• Available Values: function-declaration, function-expression, arrow-function-expression, class-declaration, class-expression and method-definition

  • function-declaration - Ignore function declarations
  • function-expression - Ignore function expressions
  • arrow-function-expression - Ignore arrow function expressions
  • class-declaration - Ignore class declarations
  • class-expression - Ignore class expressions
  • method-definition - Ignore method definitions

• Default Value: []

• Example:

​

cyclomatic_complexity_threshold

• Type: String

• Presence: optional

• Description: Specify the acceptable risk category for your project as the threshold. All functions with complexity beyond this threshold will raise an issue. For example, setting the threshold to low will flag all functions that have a cyclomatic complexity of more than 5, while setting the threshold to critical will not flag any function.

• Available Values: low, medium, high, very-high and critical

Risk category	Cyclomatic complexity range	Recommended action
low	1-5	No action is needed.
medium	6-15	Review and monitor.
high	16-25	Review and refactor. Recommended to add detailed comments if the function absolutely needs to be kept as it is.
very-high	26-50	Refactor to reduce the complexity.
critical	> 50	Must refactor this. This can make the code untestable and very difficult to understand.

• Default Value: high
• Example:

​

style_guide

• Type: String

• Presence: optional

• Description: A style guide is a set of standards that outline how code should be written and organized. Setting this will ensure that you follow established conventions, and will also allow the analyzer to raise issues for any style guide violations.

• Available Values: airbnb, google and standard

  • airbnb - Airbnb JavaScript Style Guide
  • google - Google JavaScript Style Guide
  • standard - Standard JavaScript Style Guide

• Default Value: None

• Example:

​

Sample config

​

Configuration without meta

If you use JavaScript Frameworks like React, Angular or Vue, we recommend you add meta fields to fine-tune the analyzer.

​

Configuration with meta

​

ESLint Rules & Plugins

The DeepSource JavaScript analyzer fully supports all the ESLint core JavaScript rules. Along with that, it currently supports the following ESLint plugins:

• Node

  • eslint-plugin-node

• TypeScript

  • @typescript-eslint/eslint-plugin

• React

  • eslint-plugin-react
  • @babel/eslint-plugin

• Vue

  • eslint-plugin-vue

• Flow

  • eslint-plugin-flowtype

• Ember

  • eslint-plugin-ember

• Meteor

  • eslint-plugin-meteor

• Angular

  • @angular-eslint/eslint-plugin
  • @angular-eslint/eslint-plugin-template

• AngularJS

  • eslint-plugin-angular

• Security

  • eslint-plugin-security

Custom plugins specific to your project, and other third party plugins are not supported. If a specific rule is explicitly disabled in your repository’s ESLint config, DeepSource will respect that and not raise any issues that are similar to that rule.

​

Dependency Calculation

DeepSource uses package-lock.json and yarn.lock to calculate direct and indirect dependencies. We don’t update any of the lock files.

If you have a lock file and zero (0) direct and indirect dependencies are reported, it may be because of the following reasons:

• You have not installed peerDependencies correctly.
• You are using a private node package.