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

@emkodev/emroute

v1.12.6

Published

File-based (but storage-agnostic) router with triple rendering (SPA, SSR HTML, SSR Markdown). Zero dependencies.

Downloads

696

Vulnerabilities

Powered byPowered by Snyk
  • 0High
  • 0Medium
  • 0Low

Links

Git

Maintainers

iamelruiamelru

Keywords

routerroutingspassrfile-basedframeworkbundenonodetypescriptmarkdown

Readme

Every route renders three ways from the same component: a Single Page App in the browser, server-rendered HTML, and plain Markdown. No separate API layer — prefix any route with /md/ and get text that LLMs, scripts, and curl can consume directly.

GET /projects/42          → SPA (hydrated in browser)
GET /html/projects/42     → pre-rendered HTML
GET /md/projects/42       → plain Markdown

Install

npm add @emkodev/emroute    # or bun add, pnpm add, yarn add

Works on Node, Bun, and Deno.

Quick taste

Routes are files. The filesystem is the config.

routes/
  index.page.md              → /
  projects.page.md           → /projects
  projects/[id].page.ts      → /projects/:id

A route can be a .md file, an .html template, a .ts component, or any combination. When a .page.ts exists, it controls data fetching and rendering. When it doesn't, the framework renders the companion file directly.

Documentation

Everything else — setup, routing, widgets, SSR, hydration, the runtime abstraction, design decisions — lives at emroute.emko.dev.

License

MIT