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

@plinthjs/tinker

v0.1.0

Published

Mason REPL (the Laravel Tinker equivalent).

Readme

@plinthjs/tinker

The Mason REPL, the Laravel Tinker equivalent. It is split into a testable engine and a thin interactive wrapper:

  • Tinker runs snippets in a persistent node:vm context, returning the value of the last expression and carrying top-level declarations across calls (REPL scope semantics).
  • start() boots a node:repl whose evaluator delegates to a shared Tinker, so the live REPL and Tinker.evaluate() follow the same evaluation path.

Bindings (app, registered helpers, variables you set) are exposed to evaluated code as bare identifiers. The package depends only on Node built-ins, @plinthjs/core and @plinthjs/support.

Install

npm install @plinthjs/tinker

Usage

import { Application } from '@plinthjs/core'
import { start } from '@plinthjs/tinker'

const app = new Application({ config: { app: { env: 'local' } } })

// Launch an interactive session with `app` in scope.
start({ app, prompt: 'mason> ' })
mason> app.environment()
'local'
mason> const total = [1, 2, 3].reduce((a, b) => a + b)
mason> total * 2
12

start() returns the running repl.REPLServer. It throws when called under a test runner (when VITEST is set or NODE_ENV=test), so it never attaches to the process during tests.

The engine

import { Tinker } from '@plinthjs/tinker'

const tinker = new Tinker({ context: { greet: (who: string) => `hi ${who}` } })

tinker.evaluate('1 + 1') // 2
tinker.evaluate('greet("ada")') // 'hi ada'

// Declarations persist across calls.
tinker.evaluate('const x = 5')
tinker.evaluate('function double(n) { return n * 2 }')
tinker.evaluate('double(x)') // 10

// Statement-only snippets return undefined.
tinker.evaluate('let y = 1') // undefined

// A returned promise can be awaited by the caller.
await (tinker.evaluate('Promise.resolve(7)') as Promise<number>) // 7

The vm context is seeded with host standard globals (console, JSON, Promise, fetch, URL, timers, error constructors and so on), so snippets behave as they would in a normal Node REPL.

Bindings

tinker
  .register('users', usersRepository) // a helper or service
  .setVariable('limit', 10) // a plain variable

tinker.evaluate('users.take(limit)')
tinker.getVariable('limit') // 10
tinker.evaluate('const created = 1')
tinker.getVariable('created') // 1, top-level declarations land in the scope
tinker.context() // the live bindings record

Pass an existing engine to start({ tinker }) to open a REPL over a scope you have already prepared.

Errors

Errors are never swallowed. A malformed snippet throws a real SyntaxError, and runtime errors are host Error instances, so instanceof checks work on the caller side:

tinker.evaluate('null.foo') // throws TypeError
tinker.evaluate('missingName') // throws ReferenceError
tinker.evaluate('throw "oops"') // throws Error('oops'), with the original value as `cause`