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 🙏

© 2025 – Pkg Stats / Ryan Hefner

token-scope

v1.0.0

Published

A very fast approximation of lexical-scope

Readme

token-scope

A very fast approximation of lexical-scope. It takes the source code and returns a list of all identifiers that have the potential to be references to global variables. This just parses the token stream, so it is much less thorough than lexical-scope or using uglify-js to do the same thing. It has the advantage of being vastly faster though. It is good enough to detect that jQuery does not contain require or any of the node.js globals.

Build Status Dependency Status NPM version

Installation

npm install token-scope

Usage

var detect = require('token-scope')
var inspectForRequire = detect(src)

if (inspectForRequire.indexOf('require') != -1) {
  // do more time consuming checks to search for require properly
}

Tests:

var detect = require('token-scope')

describe('detect(src, identifiers)', function () {
  it('returns an array of identifiers that might represent global variable references', function () {
    assert(detect('var x = require("foo")').indexOf('require') != -1)
    assert(detect('var x = foo("require")').indexOf('require') == -1)
  })
})

Benchmarking

To run the benchmarks, download this repository then do:

$ npm install
$ node bench/run.js

This runs 3 different scoping mechanisms on a minified copy of jQuery and report the total time for 10 iterations. They then also check that the result does not include any of the node.js globals. On my machine, this results in the output (note how token-scope results in a lot more potential globals, but still turns out to be good enough to rule out node.js globals):

name | time | output ---------------|--------|--------------- token-scope | 747ms | a,b,cy,f,cv,ck,… ugly-scope | 1457ms | setTimeout,par… lexical-scope | 2252ms | setTimeout,par…

License

MIT