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

@theholocron/scss-mixins

v0.3.0

Published

This utility droid provides a set of single-purpose, functional utilities for writing CSS within the Galaxy.

Downloads

20

Readme

(S)CSS Mixins npm

This utility droid provides a set of single-purpose, functional mixins for writing (S)CSS within the Galaxy.

Installation

$ npm install --save-dev @theholocron/scss-mixins

Table of Contents

Usage

// include all utilities with 'scss-mixins' as the namespace
// calls all mixins and will include in CSS output
@use "./node_modules/@theholocron/scss-mixins/src" as scss-mixins;

// include only a specific group of mixins
@use "./node_modules/@theholocron/scss-mixins/src/box-model" as *;
// call the mixins from this group
@include background-color();
@include border();

// use only a specific mixin
@use "./node_modules/@theholocron/scss-mixins/src/box-model/border-radius" as *;
// call the mixin you want to use
@include border-top-radius();
@include border-right-radius();

The previous examples are only a sample of what utilities are available.

Documentation

The best way to find out what's available is to check out the source code or tests but you can also take a look at the-holocron.github.io/astromech/mixins or the README which have been generated by SassDoc and sassdoc-to-markdown.

  • At-Rules - these are miscellaneous utilities that use at @ selectors such as media queries.
  • Backgrounds & Borders - these utilities all revolve around properties, such as borders and backgrounds, etc.
  • Box Model - these utilities all revolve around the box-model properties, such as width, height, overflow, margin, padding, etc. Use these to force a element to size accordingly.
  • Positioning - these utilities all revolve around positioning elements around the page, such as flexbox, floats, position, etc. Use these to force a element to layout accordingly.
  • Pseudo-Classes - these are miscellaneous utilities that affect hover, focus or active states, and nth-child selectors.
  • Text - these utilities all revolve around the typography, such as sizing, alignment, transformation, whitespace etc. Use these to force a elements text to display accordingly.

How We Track Changes Keep a Changelog

This project uses a CHANGELOG and GitHub releases which contains a curated, chronologically ordered list of notable changes for each version of a project. Read more about changelogs.

How We Version semantic-release

We use SemVer for its versioning providing us an opt-in approach to releases. This means we add a version number according to the spec, as you see below. So rather than force developers to consume the latest and greatest, they can choose which version to consume and test any newer ones before upgrading. Please the read the spec as it goes into further detail.

Given a version number MAJOR.MINOR.PATCH, increment the:

  • MAJOR version when you make incompatible API changes.
  • MINOR version when you add functionality in a backward-compatible manner.
  • PATCH version when you make backward-compatible bug fixes.

Additional labels for pre-release and build metadata are available as extensions to the MAJOR.MINOR.PATCH format.

How to Contribute Conventional Commits

Have a bug or a feature request? Looking to contribute to advance the project? Read our contribution guide or maintenance guide first in order to understand how we do things around here. Or you could look at some of our other guides below:

Where to Find Support Contributor Covenant

Looking to talk to someone or need some help? Please read our support guidelines.

License License: GPL v3

©2020 GNU General Public License v3. See LICENSE for specifics.