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

@incremental-code/last-server

v0.0.2

Published

Zero-config dev server with JSX support, built on last-router and last-act.

Readme

Last Server

A zero-config dev server for the last-act / last-router stack, with JSX support.

npx last-server src

That compiles every .jsx under src/ into a .last-server/ mirror, then starts last-router pointed at the mirror. The original src/ is untouched.

What you write

// src/page.jsx
export default function Home({ body }) {
    return <div>
        <h1>{body.title}</h1>
        <p>{body.intro}</p>
    </div>;
}
// src/[username]/page.jsx
export default function Profile({ params: { username }, body }) {
    return <div>
        <h1>Profile for {username}</h1>
        <p>{body.greeting}</p>
    </div>;
}

JSX is transformed with createElement from last-act as the factory. Fragments (<>...</>) are supported via a tiny shim that returns its children.

.ts and .tsx are also supported — types are stripped, TSX gets the same JSX treatment as JSX. Imports must use the post-compile .js extension (e.g. import { greet } from './api.js' even when the source is api.ts).

page.js and api.js files are copied through unchanged, so you can mix JS, JSX, and TS freely.

CLI

last-server <srcDir> [options]

  --port <n>     Port to listen on (default: 3000)
  --out <dir>    Compile output directory (default: .last-server)
  --no-watch     Disable file watching

Add .last-server/ to your .gitignore.

Programmatic

import { startServer } from '@incremental-code/last-server';

await startServer({
    srcDir: './src',
    outDir: './.last-server',
    port: 3000,
});

Notes

  • Each saved .jsx recompiles in place; the browser sees the new file on reload.
  • Module-level changes to server-rendered files require a server restart (Node caches import() results).
  • For routes, see the last-router readme — folder names map to URL segments, [name] becomes :name.
  • last-server exposes a built-in GET /health endpoint that returns 200 OK with body ok.