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

@uwhealth/sass-tools

v1.1.4

Published

Starter kit for Sass projects

Downloads

5

Readme

sass-tools

Central location for framework sass tools

→ View API docs

→ View sample config

Installation

# Yarn (preferred)
yarn add @uwhealth/sass-tools --dev

# NPM
npm install @uwhealth/sass-tools --save-dev

Usage

Before using sass-tools, you need to import the main entry point (index.scss) and initialize the tools. Initializing will take your configuration variables and move them to private variables used by functions and mixins elsewhere.

@import 'path/to/node_modules/@uwhealth/sass-tools/index';

// Set configuration variables
// Docs here: https://uwhealth.github.io/sass-tools/#config
// Example config here: https://github.com/UWHealth/sass-tools/blob/master/example-config.scss
// ...

// Initialize (populates configuration)
@include init;

An example configuration — for easy copy-and-paste — can be found at the root of this repo.

Deployment (publishing to npm)

Since these tools are relied on by other UW Health projects, they are available on npm. To make new versions available to npm, your new changes must be pushed to the master branch before publishing to npm.

Once your changes are pushed, you can use one of the following commands to ease the publishing/tagging process:

NOTE: You must be logged in to github and npm prior to running these commands or they will fail.

Maintenance updates (patches)

npm run patch

Minor updates (new functionality)

npm run minor

Major updates (breaking changes)

npm version major && npm publish

All commands will tag the most recent changes, update the version in package.json, and push that tag to git. The changes will then be packaged and added to npm.