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

sassport-loader

v0.2.0

Published

Use SassPort to render your Sass for WebPack! (sass-loader fork)

Downloads

16

Readme

Sass loader for webpack

This is a fork.

I forked sass-loader and left in most of the code for now - but I am planning to change this code so it will work with the SassPort module. My goal is to keep API compatibility and have this module pass the same tests as the original sass-loader, just that this one has more features.

Install

npm install sassport-loader --save

The sass/sassport-loader requires node-sass or SassPort and webpack.


Usage

Documentation: Using loaders

var css = require("!raw!sassport!./file.scss");
// => returns compiled css code from file.scss, resolves imports
var css = require("!css!sassport!./file.scss");
// => returns compiled css code from file.scss, resolves imports and url(...)s

Use in tandem with the style-loader and css-loader to add the css rules to your document:

require("!style!css!sassport!./file.scss");

NOTE: If you encounter module errors complaining about a missing style or css module, make sure you have installed all required loaders via npm.

Apply via webpack config

It's recommended to adjust your webpack.config so style!css!sass! is applied automatically on all files ending on .scss:

module.exports = {
  module: {
    loaders: [
      {
        test: /\.scss$/,
        loaders: ["style", "css", "sassport"]
      }
    ]
  }
};

Then you only need to write: require("./file.scss").

SassPort modules and options

In order to pass additional things to the SassPort .render() function, use the SassPort entry within your config:

module.exports = {
  module: {
    loaders: [
      {
        test: /\.scss$/,
        loaders: ["style", "css", "sassport"]
      }
    ]
  },
  Sassport: {
    modules: [
      // These modules will be passed to SassPort
      require('sassport-foo'),
      require('sassport-bar')
    ],
    outputStyle: "compressed",
    // ... and more ...
  }
};

See node-sass for all available options. Just note that SassPort might not support all and every option.

Imports

webpack provides an advanced mechanism to resolve files. The sass-loader uses node-sass' custom importer feature to pass all queries to the webpack resolving engine. Thus you can import your sass-modules from node_modules. Just prepend them with a ~ which tells webpack to look-up the modulesDirectories.

@import "~bootstrap/less/bootstrap";

It's important to only prepend it with ~, because ~/ resolves to the home-directory. webpack needs to distinguish between bootstrap and ~bootstrap because CSS- and Sass-files have no special syntax for importing relative files. Writing @import "file" is the same as @import "./file";

.sass files

For requiring .sass files, add indentedSyntax as a loader option:

module.exports = {
  module: {
    loaders: [
      {
        test: /\.sass$/,
        // Passing indentedSyntax query param to node-sass
        loaders: ["style", "css", "sassport"]
      }
    ]
  },
  Sassport: {
    indentedSyntax: true
  }
};

Problems with url(...)

Since Sass/libsass does not provide url rewriting, all linked assets must be relative to the output.

  • If you're just generating CSS without passing it to the css-loader, it must be relative to your web root.
  • If you pass the generated CSS on to the css-loader, all urls must be relative to the entry-file (e.g. main.scss).

More likely you will be disrupted by this second issue. It is natural to expect relative references to be resolved against the .scss-file in which they are specified (like in regular .css-files). Thankfully there are a two solutions to this problem:

Source maps

To enable CSS Source maps, you'll need to pass the sourceMap-option to the sass- and the css-loader. Your webpack.config.js should look like this:

module.exports = {
    ...
    devtool: "source-map", // or "inline-source-map"
    module: {
        loaders: [
            {
                test: /\.scss$/,
                loaders: ["style", "css?sourceMap", "sassport"]
            }
        ]
    },
    Sassport: {
        sourcemap: true
    }
};

If you want to edit the original Sass files inside Chrome, there's a good blog post. Checkout test/sourceMap for a running example.

License

MIT (http://www.opensource.org/licenses/mit-license.php)

Reminder

This is a fork. The code is likely to change since I am migrating it to use Sassport instead. Feel free to explore the code, though! :)

Fork is by: Ingwie Phoenix