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

generator-cwsass

v1.2.0

Published

An opinionated set of tools for rapid, structured Sass authorship

Downloads

5

Readme

CWsass

This Yeoman generator will provide you with a biased set of tools for rapid, structured Sass authoring.

By default when scaffolding a project using this tool, it will download node-sass. You are then given a series of options for what else to include in your project. These are based on a recommended workflow of Gulp + Libsass.

Sass documentation

Installation

Firstly, ensure you have node.js installed on your system. You can download it from here

With node.js installed, head to the command line to install Yeoman:

npm install -g yo
npm install -g generator-cwsass

Then initiate the generator from within your desired directory:

yo cwsass

A note on Browserync config

The local proxy's address you've set up may not be the same as a collaborator's (mylocalsite.dev etc). For this reason, you'll find a file called example.browserSyncConfig.js in your project. Before editing the contents of this file, rename it and save it as browserSyncConfig.js. Then edit it with your local proxy info. This file is registered in the gitignore, so you won't have conflict issues with collaborators.

If you try to run a gulp command before renaming the file, you'll receive the following error:

Error: Cannot find module './browserSyncConfig'

Gulp commands

Assuming a complete install of all options, the following command line options are available (these will be reduced if you've chosen not to install some parts):

This will start Gulp watching for changes in the sass directory, and trigger Autoprefixer and Sourcemaps upon compilation into CSS. It will also by default open your browser pointing to the proxy you've defined in browserSyncConfig.js:

gulp

The first time the Sass renders, you will find a new CSS directory is created containing the rendered, minified CSS.

If you want a one-time compilation of your Sass (with Autoprefixer and Sourcemaps) without Browsersync, run:

gulp sass

If you want your Sass linted, run:

gulp sass-lint

If you want your Sassdoc to compile the Sass documentation into a document, run:

gulp sassdoc

This will create a new directory called sassdoc, open the index.html file inside to see the documentation.

License

MIT

Credit

This work is sponsored and supported by Cameron & Wilding, a London Drupal Agency.