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

create-web-loom

v0.1.4

Published

Create a new Web Loom project powered by Vite

Readme

create-web-loom

Scaffold a new Web Loom starter on top of a Vite project.

npm create web-loom@latest
# or
pnpm create web-loom
# or
yarn create web-loom
# or
bun create web-loom

What it does

  1. Runs create-vite interactively.
  2. Detects the generated framework + JS/TS variant.
  3. Installs published @web-loom/* packages.
  4. Applies a template overlay from src/templates/<framework>/<variant> plus src/templates/shared.

The overlay intentionally replaces Vite's runnable starter entry files so npm run dev starts in a Web Loom MVVM starter immediately. create-vite is invoked with --no-immediate so it cannot auto-install and start the dev server before Web Loom post-steps finish.

If the scaffold cannot be mapped to a supported framework template, the CLI exits with a clear unsupported-scaffold error.

Framework support

| Framework | Variants | Overwritten runnable files | | --- | --- | --- | | React | TS, JS | src/App.tsx / src/App.jsx | | Preact | TS, JS | src/app.tsx / src/app.jsx | | Vue | TS, JS | src/App.vue | | Solid | TS, JS | src/App.tsx / src/App.jsx | | Svelte | TS, JS | src/App.svelte | | Lit | TS, JS | src/my-element.ts / src/my-element.js | | Vanilla | TS, JS | src/main.ts / src/main.js | | Qwik | TS-first | src/routes/index.tsx |

Shared files are copied for every framework (for example src/viewmodels/CounterViewModel.ts).

Template source of truth

Template content is file-based and lives in:

  • src/templates/shared/**
  • src/templates/<framework>/<variant>/**

During build, templates are copied into dist/templates/**. Runtime boilerplate injection reads from dist/templates so published CLI builds are self-contained.

Usage

# Interactive
npm create web-loom@latest

# Pass project name
npm create web-loom@latest my-app

After generation:

cd my-app
npm install
npm run dev

Installed packages

All currently published core packages are installed:

  • @web-loom/mvvm-core
  • @web-loom/store-core
  • @web-loom/query-core
  • @web-loom/event-bus-core
  • @web-loom/event-emitter-core
  • @web-loom/signals-core
  • @web-loom/design-core
  • @web-loom/ui-core
  • @web-loom/ui-patterns

If a package is temporarily unavailable on npm, the installer retries one package at a time and skips only the unavailable package(s) instead of failing the whole scaffold.

Local development

cd packages/create-web-loom
npm run build
npm run test

# Try locally
node dist/index.js my-test-app

# Check publish contents
npm pack --dry-run