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

ruby-sass

v0.0.3

Published

Ruby Sass binding for Node.js

Downloads

79

Readme

node-ruby-sass

Build Status

WORK IN PROGRESS...

This Node module is an attempt to provide a faster binding to Ruby Sass than currently available.

Explanation: Sass in a Rails app with LiveReload seems much faster than things like gulp-ruby-sass. I'm guessing this is because Rails runs Sass using the same Ruby process every compile, avoiding Ruby spin-up time, and benefiting from in-memory caching. This module tries to do something similar. Benchmarks to follow.

Installation

$ npm install ruby-sass

Usage

var sass = require('ruby-sass');

sass('path/to/something.scss', function (err, css) {
    // got the css (or an error with a *sass* stack trace)
});

Repeated calls should be faster than the first one.

You can also pass options as a second argument.

Options

  • loadPaths (array)
  • sourcemap (boolean)

Alternative API

var Sass = require('ruby-sass').Sass;

var sass = new Sass();

sass.compile(filename, options, callback); // same as the `sass` function in standard API.

Constructor options

These are optional.

  • port – which port to use
  • basePort (default: 8500) – if you don't set a port, portfinder will be used to find one manually, starting at this base port.

To do

  • source maps
  • ~~make it so you don't have to wait for ready~~
  • ~~kill ruby process when node exits or on uncaught exception~~
  • ~~make a way to stop it manually~~
  • write benchmarks
  • see if repeat runs on the same file are actually any faster. if not, look at using Sass::Plugin (?)
  • make post install script to check if required gems are installed and print instructions to install them (or just install them?)
  • ~~pass in sass options per-file, not per-instance~~
  • ~~simplify api~~
  • test it on windows

Licence

MIT