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

@kredati/ludus-repl

v0.1.4

Published

A basic live-reloading node repl

Downloads

9

Readme

ludus-repl

A basic live-reloading repl

What

A node repl that live-reloads a given module (esm or cjs) and its dependencies, for a more interactive coding experience. It's not very sophisticated: it watches for changes only in node's process.cwd, so it's best to invoke it from the root of the project.

Installation

npm i @kredati/ludus-repl --save-dev

Use

npx repl ./src/foo  # starts a repl for ./src/foo.js

Context

This repl does not load your module as a script (i.e. using the .load command). Instead, it loads just what all is in the file in question's exports (esm [export {foo}] or cjs [module.exports = {foo}]). If you wish to expose local variables that are not exported to the repl, the repl also mounts a global variable, __contextualize, which adds local variables to the repl context. It takes a record (object literal), and puts everything in that record into context in the repl, using the keys in the object as variable names. In the repl, there is also a context variable, __context, which will show you what the repl has loaded.

Consider the following module:

const foo = 'foo'

const bar = () => foo

export {bar}

The repl will only load bar. If you wanted to also include foo in the repl context, you would add __contextualize({foo}). At which point, on saving the file, the new context would be

Known issues

The repl can handle errors when reloading the module it's working on, but it will fall over on uncaught errors in its dependencies. So if you're editing dependencies instead of the loaded file, be careful to avoid parsing errors.

Also, the repl works in a different realm than modules run in, so subtle (and not-so-subtle) errors around global variables can creep in. Be especially careful of prototype chains; use Array.isArray.