By default, Code Dx will pass –ignore-pattern **/node_modules/*

Code Dx supports user-defined .eslintrc and .eslintignore ESLint config files. Place the
file(s) within the tool-data/eslint directory, or within a project-specific subdirectory. Files
should follow the format defined by ESLint. You can use the js, yml, json, or eslintrc
formats. In the event that there are multiple config files present in different formats,
Code Dx will follow the same priority that ESLint uses. ESLint will also use any
.eslintrc config files uploaded in the project as defined by the rules explainedhere.
Additionally, Code Dx will search for an .eslintignore file in the root directory of the
uploaded zip file. The .eslintignore file in the zip will take precedence over the
.eslintignore file in the tool-data/eslint or project-specific directories. If you use a custom
config, be sure to adjust your Tool Configuration. By default, only the
recommended ESLint rules are enabled.

Code Dx also supports user-defined extension of the default eslintrc.json file. For
users wanting to add small tweaks to the default configuration, a eslint-config-extra.js
can be placed within the tool-data/eslint directory, or within a project-specific
subdirectory (a directory whose name is the numeric id of the Code Dx project), as
with the custom .eslintrc and .eslintignore files mentioned in the previous paragraph.
When running ESLint, Code Dx will search for this “extra” config file and, if present,
will include it as an extension of its default ESLint config file. The contents of the
eslint-config-extra.js file should be in the form module.exports = { … }, where the … is
replaced by your custom configuration as defined in the ESLint configuration guide.

Important note about using a custom .eslintignore file: If an .eslintignore file is
neither found in the uploaded zip file nor provided in the tool-data/eslint directory,
Code Dx will pass –ignore-pattern **/node_modules/* as a command-line argument to
ESLint. If you want to provide an .eslintignore file, it is a good idea to include the
**/node_modules/* pattern in that file; linting the contents of your third-party
dependencies is not recommended, and in some cases can cause ESLint to fail.

Several ESLint plugins are made available when running as a bundled tool in Code
Dx:

• eslint-plugin-security: enabled by default
• eslint-plugin-scanjs-rules: enabled by default
  
  • eslint-plugin-no-unsafeinnerhtml: included as a requirement of scanjs-
    rules
• eslint-plugin-xss: enabled by default
• eslint-plugin-html: enabled by default
• eslint-plugin-react: enabled by default
• babel-eslint: enabled by default

Any of these plugins can be used in or excluded from your user-defined configs. All
plugins use their default or recommended rules and settings, except for no-location-
href-assign from eslint-plugin-xss. For this rule, Code Dx uses encodeURIComponent for
the escapeFunc option instead of the default escape function, which has been
deprecated. More information about how to configure these plugins can be found on
their respective npmjs or github pages.

By default, Code Dx will run ESLint on .js, .html, and .htm files. If you want to change
this behaviour, you can specify a comma separated list of file extensions with the
eslint.extensions setting in your codedx.props file. You do not need to include the . with
each file extension (eslint.extensions = js,html,htm). Note that if you decide not to use the
html plugin in your custom configs, you must use this setting to specify that you want ESLint to only run on .js files. Otherwise it will try to scan any .html and .htm files
it finds as javascript, which will cause ESLint parsing errors.

If you want to use your own ESLint environment, you can specify the path to it in
your codedx.props file with the eslint.path setting. Code Dx expects that the provided
directory will point to the folder containing ESLint’s bin folder. Code Dx will also try
to find any of the supported ESLint config files in this directory. Note that if you use
the global or project config files as described above, they will take precedence over
the ones in this folder.