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

ember-cli-ruby-sass

v3.2.1

Published

Use libsass to preprocess your ember-cli app's files, with support for include paths

Downloads

5

Readme

ember-cli-ruby-sass

This is a fork of ember-cli-ruby-sass. It is using Ruby's implementation os SASS instead of libsass.

Use node-sass to preprocess your ember-cli app's files, with support for source maps and include paths.

Installation

npm install --save-dev ember-cli-sass

Usage

By default this addon will compile app/styles/app.scss into dist/assets/app.css and produce a source map for your delectation.

Or, if you want more control then you can specify options using the sassOptions config property in config/environment.js:

ENV.sassOptions =  {...}
  • .includePaths: an array of include paths
  • .sourceMap: controls whether to generate sourceMaps, defaults to true in development. The sourceMap file will be saved to options.outputFile + '.map'
  • .ext: the extension to look for, defaults to scss
  • See broccoli-sass for a list of other supported options.

Processing multiple files

If you need to process multiple files, it can be done by configuring the output paths in your Brocfile.js:

var app = new EmberApp({
  outputPaths: {
    app: {
      css: {
        'app': '/assets/application-name.css',
        'themes/alpha': '/assets/themes/alpha.css'
      }
    }
  }
});

Upgrading from a previous version

In previous versions the sassOptions config property could be added to the EmberApp constructor in Brocfile.js, although this is still supported it is recommended to use the above usage.

If you were using the .inputFile and .outputFile options, this is now done by configuring the output paths in your Brocfile.js

Example

The following example assumes your bower packages are installed into bower_components/.

Install some SASS:

bower install --save foundation

Specify some include paths in config/environment.js:


ENV.sassOptions = {
  includePaths: [
    'bower_components/foundation/scss'
  ]
}

Import some deps into your app.scss:

@import 'foundation'; /* import everything */
/* or just import the bits you need: @import 'foundation/functions'; */

Source Maps

Be aware that there are some issues with source maps in broccoli-sass. The source maps it generates will at least show you the source file names and line number in your dev tools. When we've got a better solution in broccoli-sass you'll be able to click through to view and update the SASS files in the dev tools \o/.