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

sass-jest

v0.1.7

Published

Unit test Sass using Jest

Downloads

112

Readme

sass-jest

sass-jest is a Sass preproccessor for Jest that lets you test projects with Sass. The API used matches the excellent sass-true library.

Install

To use this in your project, run:

npm install --save-dev sass-jest

If you don't already have jest installed,

npm install --save-dev jest sass-jest

Modify your project's package.json so that the test and jest section looks something like:

{
    "scripts": {
        "test": "jest"
    },
    "jest": {
        "moduleFileExtensions": [
            "js",
            "scss"
        ],
        "transform": {
            "^.+\\.scss$": "sass-jest"
        },
        "testRegex": "__tests__/.*\\.(js|scss)$"
    }
}

Import the mixins to your test file, like any other Sass file:

@import "sass-jest";

Usage

sass-jest follows Jest's structure for writing tests by using describe/it.

@include describe('Zip [function]') {
    @include it('Zips multiple lists into a single multi-dimensional list') {
    
        // Assert the expected results
        @include assert-equal(
            zip(a b c, 1 2 3),
            (a 1, b 2, c 3)
        );
        
        @include assert-true(true);
        @include assert-false(false);
    }
}

Asserting an @error was raised

Using @error will cause the Sass compiler to bail out with the given message, to get around this sass-jest converts all @error calls to a return statement and handles catching the error message for you.

@function throws-error() {
    @error "Thrown error"
}

@include describe ('Error') {
    @include it ('Captures the error and asserts its value') {
        // Make sure you call the code that will throw the error within the "it" mixin
        $dummy: throws-error();
        @include assert-error-raised ("Thrown error");
    }
}

Note: As @error is converted to a return, functions that call functions that raise errors will have different behavior.

Test CSS output from mixins

One can use the assert mixin to compare the compiled CSS that your code produces.

@include describe('css comparisons') {
    @include it('compares two blocks of css') {
        @include assert {
            @include output {
              @include font-size('large');
            }
            
            @include expect {
                font-size: 2rem;
                line-height: 3rem;
            }
        }
    }
}

Test Environment

If you do not have any tests that require jsdom then you can set Jest's test environment to node instead as this will reduce the startup time for your tests to run.

{
    "jest": {
      "testEnvironment": "node"
    }
}

Todo

  1. Add switch to turn of @error converting
  2. Provide better error messages when a test fails
  3. Support source maps to show where in the sass file an error was raised
  4. Parse output blocks into an AST and strip whitespace/comments for less fragile comparisons