Package Exports
- sass-lint
- sass-lint/bin/sass-lint
- sass-lint/lib/config
- sass-lint/lib/rules
This package does not declare an exports field, so the exports above have been automatically detected and optimized by JSPM instead. If any package subpath is missing, it is recommended to post an issue to the original package (sass-lint) to support the "exports" field. If that is not possible, create a JSPM override to customize the exports field for this package.
Readme
Sass Lint 
A Node-only Sass linter for both sass and scss syntax! See the sample config file to see how to write a configuration file, and our release issue to track what's missing for an initial release.
Creating Rules
Our AST is Gonzales-PE. Each rule will be passed a node as the AST is traversed. There are many different node types that may be traversed, and an extensive API for working with nodes. 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. 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. 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!