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

@cfdez11/vex

v0.11.0

Published

A vanilla JavaScript meta-framework with file-based routing, SSR/CSR/SSG/ISR and Vue-like reactivity

Readme

@cfdez11/vex

npm JavaScript Node.js

A vanilla JavaScript meta-framework built on Express.js with file-based routing, multiple rendering strategies (SSR, CSR, SSG, ISR), streaming Suspense, and a Vue-like reactive system — no TypeScript, no bundler.

Requires Node.js >= 18.

Installation

npm install @cfdez11/vex

Quick Start

mkdir my-app && cd my-app
npm init -y
npm install @cfdez11/vex
npm install -D tailwindcss npm-run-all

Update package.json:

{
  "type": "module",
  "scripts": {
    "dev":     "run-p dev:*",
    "dev:app": "vex dev",
    "dev:css": "npx @tailwindcss/cli -i ./src/input.css -o ./public/styles.css --watch",
    "build":   "vex build",
    "start":   "vex start"
  }
}

Create the minimum structure:

mkdir -p pages src public
echo '@import "tailwindcss";' > src/input.css
npm run dev
# → http://localhost:3001

Documentation

Roadmap

  • [x] File-based routing with dynamic segments
  • [x] SSR / CSR / SSG / ISR rendering strategies
  • [x] Incremental Static Regeneration with background revalidation
  • [x] Static path pre-generation (getStaticPaths)
  • [x] Auto-generated server and client route registries
  • [x] Streaming Suspense with fallback UI
  • [x] Vue-like reactive system (reactive, computed, effect, watch)
  • [x] Nested layouts per route
  • [x] SPA client-side navigation
  • [x] Prefetching with IntersectionObserver
  • [x] Server-side data caching (withCache)
  • [x] HMR (hot reload) in development
  • [x] Component props (xprops)
  • [x] vex/ import prefix for framework utilities
  • [x] vex.config.json — configurable srcDir and watchIgnore
  • [x] Published to npm as @cfdez11/vex
  • [x] VS Code extension with syntax highlighting and go-to-definition
  • [ ] Refactor client component prop pipeline
  • [ ] esbuild minification for production builds
  • [ ] esbuild source maps in dev mode
  • [ ] esbuild browser target config
  • [ ] esbuild code splitting for shared dependencies
  • [ ] Devtools
  • [ ] TypeScript support (framework + user code)
  • [ ] Improved VS Code extension
  • [ ] Theme syntax
  • [ ] Docs page
  • [ ] Authentication middleware
  • [ ] CDN cache integration
  • [ ] Fix Suspense marker replacement with multi-root templates
  • [ ] Refactor template engine — replace htmlparser2 + dom-serializer parse/transform/serialize pipeline with a build-time template compiler (à la Vue/Svelte) that generates render functions. Current limitations: htmlparser2 decodes HTML entities on parse and dom-serializer doesn't re-encode them correctly (&lt; inside <pre> becomes literal <); whitespace inside <pre>/<code> is incorrectly stripped; workarounds patched but root cause is architectural. Build-time compilation would eliminate all these issues and improve runtime performance.