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 🙏

© 2026 – Pkg Stats / Ryan Hefner

sass-lexer

v1.0.1

Published

Adapted from [scss-parser](https://npmjs.org/package/scss-parser).

Readme

sass-lexer

Adapted from scss-parser.

const tokenize = require('sass-lexer');

// takes a string
const tokens = tokenize(input);

// get the next token
tokens.next();          // => array

// look ahead
tokens.peek(offset);    // => array

// check for end of file
tokens.eof();           // => boolean

// throw an error with line & column
tokens.err('oh crap');

The next and peek methods return null if no more tokens exist.

Tokens are arrays of the following shape:

  • 0: string type
  • 1: string value
  • 2: number length
  • 3: number start line
  • 4: number start column

You can track the character offset yourself:

let offset = 0;
while (!tokens.eof()) {
  const tok = tokens.next();
  //
  // do your thing here...
  //
  // now, update the character offset.
  offset += tok[2];
}

The values of tok[1].length and tok[2] are not always equal, so be sure to use tok[2] when calculating the character offset.

Token types

  • atrule (does not include @ in the value)
  • color_hex (does not include # in the value)
  • comment (does not include // or /* or */ in the value)
  • identifier
  • number (does not include units like px in the value)
  • operator
  • punctuation
  • space (mix of and \t and \n in the value)
  • string (does not include " or ' in the value)
  • variable (does not include $ in the value)

Parser utils

const utils = require('sass-lexer/utils');

// Return true if `tok` is truthy and `tok[0]` equals the given string.
utils.isType(tok, 'space');

// Return true if `tok` is truthy and `tok[1]` equals the given string.
utils.isValue(tok, ':');

// Return true if `tok` is truthy and `tok[0]` is not the given string.
utils.notType(tok, 'space');

// Return true if `tok` is truthy and `tok[1]` is not the given string.
utils.notValue(tok, ':');

// Throw an error if `tok` is falsy or `tok[0]` is not the given string.
utils.assertType(tok, 'space');

// Throw an error if `tok` is falsy or `tok[1]` is not the given string.
utils.assertValue(tok, ':');