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

inspect-code

v1.0.0

Published

Run code and get the value of every expression.

Readme

inspect-code

Run code and get every expression's value. Powering js-playgrounds.

npm version build status dependency status dev dependency status ISC-licensed chat on gitter

How it works

inspect-code takes a string of code, instruments it to spy on every expression and uses lolex to make setTimeout & co. run sync in the end. After running it inside Node's vm, it returns every expression, with its code and values. This is similar to what JS code coverage tools do.

Note that, because this module executes the code instead of doing static analysis, it is limited by runtime limitations such as runtime errors.

Caveats

  • The code has only access to things inside the sandbox.
  • Code that does any stack trace magic will behave differently.
  • Parsing & instrumenting will make it slower than vm.runInNewContext (run the benchmarks).
  • There are unsolved problems like spread operators, async/await, etc.

Installing

npm install inspect-code

Usage

Imagine you want to analyze the following piece of code.

const code = `\
const a = x => x - 1
const b = [1, 2, 3]
const c = b[a(b.length)]
c + 1`

inspect will return a list of results, each with start, end, code, value and isException.

const inspect = require('inspect-code')

console.log(inspect(code))
[
	{
		start:  { line: 0, column: 15 },
		end:    { line: 0, column: 20 },
		code:   'x - 1',
		values: [ 2 ]
	}, {
		start:  { line: 1, column: 10 },
		end:    { line: 1, column: 19 },
		code:   '[1, 2, 3]',
		values: [ [ 1, 2, 3 ] ]
	}, {
		start:  { line: 2, column: 14 },
		end:    { line: 2, column: 22 },
		code:   'b.length',
		values: [ 3 ]
	}, {
		start:  { line: 2, column: 12 },
		end:    { line: 2, column: 23 },
		code:   'a(b.length)',
		values: [ 2 ]
	}, {
		start:  { line: 2, column: 10 },
		end:    { line: 2, column: 24 },
		code:   'b[a(b.length)]',
		values: [ 3 ]
	}, {
		start:  { line: 3, column: 0 },
		end:    { line: 3, column: 5 },
		code:   'c + 1',
		values: [ 4 ]
	}
]

Contributing

If you have a question, found a bug or want to propose a feature, have a look at the issues page.