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

@evjs/cli

v0.1.5

Published

Command-line wrapper for the evjs framework

Downloads

2,031

Readme

@evjs/cli

Thin command-line wrapper for the evjs fullstack framework.

Install

npm install -g @evjs/cli

Convention over Configuration

No configuration file is needed. ev dev and ev build delegate to @evjs/ev and inject the default utoopack adapter:

  • Entry: ./src/main.tsx
  • HTML: ./index.html
  • Client dev server: port 3000
  • API server (dev): port 3001
  • Server functions auto-discovered via "use server" directive

Commands

| Command | Description | |---------|-------------| | ev dev | Start dev server (client HMR + API watch) | | ev build | Production build (client + server) |

Scaffolding: Use npx @evjs/create-app to scaffold a new project.

ev dev

Uses the default bundler adapter directly (no temp config files):

  1. dev server (port 3000) — client bundle with HMR.
  2. Node API Server (port 3001) — auto-starts when server bundle is emitted, uses node --watch.

ev build

Runs the production build through @evjs/ev with NODE_ENV=production:

  • dist/client/ — optimized client assets with content hashes.
  • dist/server/main.[hash].js — server bundle (entry discovered via dist/server/manifest.json).

Configuration

Create ev.config.ts in the project root (optional):

import { defineConfig } from "@evjs/ev";

export default defineConfig({
  entry: "./src/main.tsx",
  html: "./index.html",
  dev: { port: 3000 },
  server: {
    dev: { port: 3001 },
  },
});

The dev and server.dev fields accept extra options that are merged with defaults.

Project Structure

my-app/
├── ev.config.ts          # optional config
├── index.html            # HTML template
├── package.json
├── tsconfig.json
└── src/
    ├── main.tsx           # app bootstrap (keep minimal)
    ├── routes.tsx         # route tree + components
    ├── api/               # server functions
    │   ├── users.server.ts
    │   └── posts.server.ts

        └── auth.ts

Common Mistakes

  1. Don't create custom bundler config file — use ev.config.ts instead
  2. Don't install bundler internals manually — the default adapter is provided by @evjs/cli
  3. Config file must be ev.config.ts — not evjs.config.ts
  4. Import defineConfig from @evjs/ev — not from @evjs/server

Bundled Dependencies

Users do NOT need to install these — they're included through @evjs/cli:

  • @evjs/bundler-utoopack
  • @evjs/build-tools
  • the bundler's underlying compiler dependencies