Comparing version 0.1.0-alpha.1 to 0.1.0-alpha.2
{ | ||
"name": "sass-lint", | ||
"version": "0.1.0-alpha.1", | ||
"version": "0.1.0-alpha.2", | ||
"description": "Sass linter. Compatible but different from scss-lint", | ||
@@ -5,0 +5,0 @@ "main": "index.js", |
# Sass Lint [![npm version](https://badge.fury.io/js/sass-lint.svg)](http://badge.fury.io/js/sass-lint) | ||
A Node based [Sass](http://sass-lang.com/) linter. Designed (eventually) as a drop-in replacement for [SCSS-Lint](https://github.com/causes/scss-lint). | ||
A Node-only Sass linter for both `sass` and `scss` syntax! See the sample [config file](https://github.com/sasstools/sass-lint/blob/playground/lib/config/sass-lint.yml) to see how to write a configuration file, and our [release issue](https://github.com/sasstools/sass-lint/issues/6) to track what's missing for an initial release. | ||
## Creating Rules | ||
Our AST is [Gonzales-PE](https://github.com/tonyganch/gonzales-pe/tree/dev). Each rule will be passed a node as the AST is traversed. There are many different [node types](https://github.com/tonyganch/gonzales-pe/blob/dev/doc/node-types.md) that may be traversed, and an extensive [API for working with nodes](https://github.com/tonyganch/gonzales-pe/tree/dev#api). The file of the rule must have the same name as the name of the rule. All of the available rules are in our [rules directory](https://github.com/sasstools/sass-lint/tree/playground/lib/rules). Default options will be merged in with user config. | ||
``` | ||
TODO: Should we traverse the whole node tree and pass in each node to each rule, or pass the whole AST to each rule to let them do with it what they'd like? Originally it was the later to give the widest birth of flexibility, but thought the former may be faster because each rule wouldn't have to traverse the whole tree. Thoughts? | ||
``` | ||
## Road to Release | ||
Keep track of the [path to a full release](https://github.com/sasstools/sass-lint/issues/6). If you can help contribute by writing rules that are missing (or have a rule you really want to see in there and add), please do so! PRs accepted! |
License Policy Violation
LicenseThis package is not allowed per your license policy. Review the package's license to ensure compliance.
Found 1 instance in 1 package
License Policy Violation
LicenseThis package is not allowed per your license policy. Review the package's license to ensure compliance.
Found 1 instance in 1 package
Major refactor
Supply chain riskPackage has recently undergone a major refactor. It may be unstable or indicate significant internal changes. Use caution when updating to versions that include significant changes.
Found 1 instance in 1 package
17224
15
0