Upgrade Guide

If you are planning on using css-coding-standards, and have previously used WDS-Coding-Standards, please follow this guide to upgrade your setup.

Note, installing css-coding-standards will not just magically work if you have .editorconfig files, .sass-lint.* files, or stylelint configurations in your project tree that point to other configurations.

---

First, remove WDS-Coding-Standards

Note you do not have to do the below steps removing global sass-lint, but it will ensure better compatibility with css-coding-standards.

---

Use npm -g list --depth=0 and see if the below packages are in the list. If it is, it is recommended you remove it from your global install using:

---

Remove sass-lint if it is installed globally

npm -g remove sass-lint

---

Then, install using steps outlined here.

---

Editor Configuration

If you were previously using WDS-Coding-Standards you may have your editor configured to use global sass-lint settings, for instance, in Sublime Text, it looks like:

      "sass": {
          "disable": false,
          "args": [
            "--config=~/.composer/vendor/webdevstudios/wds-coding-standards/WebDevStudios/.sass-lint.yml"
          ],
          "excludes": []
      },

You will need to disable any --config option pointing to globally installed sass configurations. You will also need to disable any executable paths pointing to any specific path.