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-weft

v0.1.6

Published

npm create weft — a weft application, with a page you can open.

Readme

create-weft

A new weft application, with a page you can open.

npm  create weft@latest my-app
pnpm create weft my-app
yarn create weft my-app
bun  create weft my-app
cd my-app
npm install
npm run dev          # http://localhost:3000

Templates

| | | | ----------------- | ---------------------------------------------------------------------------------------------- | | app (default) | A layout, three routes, a fragment with its own CSS, a slot, and a real mutation you can press | | minimal | One route, and nothing else |

npm create weft my-app -- --template minimal

Already inside a project? The framework's own CLI scaffolds too: npx weft create my-app.

What it writes

Every file is one the framework will actually read, and each says what it is for. The page it produces is a real page: it renders through the kernel, its CSS is linked the way a component's CSS is linked, and its buttons dispatch a real intent that also works with JavaScript switched off. A scaffold whose output is a placeholder teaches nothing about the framework it is scaffolding.

A non-empty target directory is refused rather than merged — E_NOT_EMPTY, naming what is in the way.

This package is a shim, deliberately. The templates and the scaffolder live in the @weftjs/core package itself, because a scaffold that ships its own copy of them is a scaffold that will generate an application the framework has stopped supporting.

License

MIT