A Node-only Sass linter for both
Patterns to include in execution and reports.
Patterns to exclude from execution and reports.
-c, --config options.
Amount of CPU. The default machine has
0.25 CPU with
960 MiB RAM.
Below is the list of options that are supported:
-c, --config [path] path to custom config file -i, --ignore [pattern] pattern to ignore. For multiple ignores, separate each pattern by `, ` within a string -s, --syntax [syntax] syntax to evaluate the file(s) with (either sass or scss)
Note: Specifying the
--max-warningsoption has no effect on Inspecode, therefore the option is deprecated. Instead, consider using
num-issues:as described below for telling Inspecode the threshod of the number of warnings.
No tool specific severity levels are available.
Note: The incremental analysis is disabled if any kinds of configuration files are changed. The files recognized as configuration files are as follows:
- Configuration files:
- Files specified in
- Files specified to
- If none of the above configuration files are found:
- Files specified to
package.jsonat the repository root
No tool specific experimental options are available.
With default options:
inspecode: tools: sass-lint: default
With custom machine:
inspecode: tools: sass-lint: machine: cpu: 1.5 # 1.5 CPU, 5760 MiB RAM
With custom options:
inspecode: tools: sass-lint: options: --ignore: - tests/**/*.scss - dist/other.scss
With a configuration file:
inspecode: tools: sass-lint: config-file: app/config/.sass-lint.yml
The above configuration is equivalent to:
inspecode: tools: sass-lint: options: --config: app/config/.sass-lint.yml
With a threshold of the number of warnings (the alternative to
inspecode: tools: sass-lint: thresholds: num-issues: warning: 100
If no configuration files are specified via
options field, Inspecode first lets Sass Lint to find configuration files in your repository.
See https://github.com/sasstools/sass-lint#configuring about how Sass Lint looks for configuration files.
In addition, if Sass Lint cannot find any configuration files, Inspecode also walks the file tree in lexical order in your repository to find a configuration file named
.sasslintrc and specifies the file first found to Sass Lint automatically via
Note: Inspecode ignores specific configuration files while searching. See Configuration > Tool Configuration > Field:
If the configuration file detected by Inspecode is not the one you want to use or you do not want to use any configuration files, you can disable Inspecode from detecting configuration files by explicitly setting an empty string to
config-file field like below:
inspecode: tools: sass-lint: config-file: ""