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

@lediv/build

v0.2.0

Published

Isomorphic site builder for Lediv projects

Vulnerabilities

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

Links

Maintainers

lmgonzalveslmgonzalves

Keywords

ledivbuildstatic-sitehtml

Readme

@lediv/build

Isomorphic site builder for Lediv projects. Turns a flat list of project source files (pages/, components/, public/) into the files of a static site: resolved component trees, evaluated template logic, injected font CSS, and copied public assets.

You probably want @lediv/vite-plugin. This package is published because the plugin depends on it, not because it is meant to be called directly. It is the build core both the plugin and Lediv's server-side publishing run, so a project built locally and the same project published from Lediv cannot drift; a test asserts they produce byte-identical page HTML.

It has no filesystem, no Vite, and no Node built-ins: sources go in as strings and bytes, built files come out the same way. That is what lets it run in a Cloudflare Worker and in a Vite build alike.

Usage

npm install @lediv/build
import { buildSite } from '@lediv/build';

const { files, routes, fonts } = await buildSite(
  [
    { name: 'pages/index.html', input: '<html>...</html>' },
    { name: 'components/Header.html', input: '<header>...</header>' },
    { name: 'public/logo.svg', input: bytes },
  ],
  { preloadFonts: true },
);

Nothing is minified unless you pass a minify function. Page output is the HTML you authored.

Failures throw BuildSiteError, which carries a code and, where the failure belongs to one page, that page. The options, the result shape, the error codes and the exported helpers (buildPageHtml, contentTypeFor, pagePathToRoute, pagePathToOutputPath) all ship with type definitions; read those rather than a table here that can go stale.

A _redirects file at the root of the source is left out of the output rather than published as content. Interpreting it is the caller's job; the rule syntax is documented at https://lediv.com/docs/redirects.

License

MIT