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

@phanty/sass-bundler

v1.0.2

Published

A package for bundling page-specific SASS/SCSS

Downloads

3

Readme

sass-bundler

A quick and dirty npm package for bundling page-specific SASS/SCSS.

Installation

npm install --save-dev @phanty/sass-bundler

Usage

@import and @use statements in SASS must be preceeded by !bundler, e.g. @use "!bundler/_partial.scss".

For the bundler to recognize partials, their filename must be preceeded by _.

Outputs partials used by all SASS files to a single file.

Example

Input

a.scss

@use "!bundler/_partial1.scss"

#a{
  color: red;
}

b.scss

@use "!bundler/_partial1.scss"

#b{
  color: green;
}

_partial1.scss

span{
  font-weight: bold;
}

Compiles to

a.css

#a{
  color: red;
}

b.css

#b{
  color: green;
}

shared.css

span{
  font-weight: bold;
}

CLI

sass-bundler [command] [options]

Commands:

  • help - Print help
  • init - Generate a default config file in current directory
  • build - Build and bundle SASS/SCSS files. If sass-bundler.config.js isn't in the project root, uses default config.
  • watch - Watch SASS/SCSS files for changes. If sass-bundler.config.js isn't in the project root, uses default config.

Options:

  • --config [string] - Path to config file
  • --<CONFIG_ARG> [string] - Overwrite config argument

API

class Bundler(config?)

  • .buildAll() - Builds and bundles all SCSS/SASS files according to config
  • .watch() - Watches files for changes. Incrementally compiles.

Configuration

  • sassDir: [string] - ./sass - Path to the SASS/SCSS directory
  • outDir: [string] - Default: ./build - Path to the output directory
  • verbose: [boolean] - Default: false - If true, prints which files have been compiled
  • sharedPath: [string] - Default: ./build/shared.css - Path to the file where to output the shared css