npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

brackets-sass-lint

v1.11.1

Published

Brackets extension for pure Node.js Sass linting

Downloads

5

Vulnerabilities

Powered byPowered by Snyk
  • 0High
  • 0Medium
  • 0Low

Links

Git

Maintainers

petetntpetetnt

Keywords

brackets-extensionsassscsslintnodebrackets

Readme

Brackets Sass Lint

Brackets extension for pure Node.js linting of sass and scss syntaxed files, powered by Sass-Lint. No external dependencies needed!

Installation

Due to an issue with brackets-registry, this package is only available on brackets-npm-registry.

To install it, follow the following steps:

  1. Install brackets-npm-registry
  2. Click the npm-button on your taskbar
  3. Install brackets-sass-lint.

When the issue is fixed...

You can always find the latest version of brackets-sass-lint from the Brackets Extension Manager.

  1. Open Brackets
  2. Select File -> Extension Manager
  3. Search for brackets-sass-lint
  4. Click Install
  5. Close the Extension Manager window

Alternatively you can install it straight from this GitHub repo

  1. Open Brackets
  2. Select File -> Extension Manager
  3. Click Install from URL...
  4. Enter the following URL: https://github.com/petetnt/brackets-sass-lint
  5. Click Install
  6. Close the Extension Manager window

Or you can just clone the repo to %Brackets Extension Folder%/user/ with

git clone https://github.com/petetnt/brackets-sass-lint

Rules

By default, the linter uses built-in default, similar to those set in this projects .sass-lint.yml.

To override these defaults, create file called .sass-lint.yml on your project root. You can use this sample config as the base for your own configurations.

Todo

  • [ ] Finish writing the unit tests under unittests.js

Versions

  • 1.11.1

    • Version bump
    • Updated sass-lint to 1.10.0

  • 1.10.0

    • Version bump
    • Updated sass-lint to 1.10.0

  • 1.0.0

    • Version bump
    • Update sass-lint to 1.7.0

  • 0.0.2

    • Release on brackets-npm-registry because of on-going issue with the brackets-registry

  • 0.0.1

    • First release!
    • Lint your SASS and SCSS files with ease!

Contributing

Contributions are welcome! Send a PR or submit an issue! Make sure your changes pass ESLint and create new unit tests if needed.

Releasing as a zip file

Generate the petetnt.brackets-sass-lint zip file by bumping up the version number in package.json, committing your changes and running npm run release. You can then find the new zip file under release/.

License

MIT