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 🙏

© 2024 – Pkg Stats / Ryan Hefner

@static-pages/core

v7.0.0

Published

General purpose static pages renderer.

Downloads

39

Readme

Static Pages / Core

Build Status Coverage Status npms.io (quality) Maintenance

Yet another static pages generator? Yes! Because I browsed the whole jamstack scene, but could not find one which

  1. can read input from any source (YAML, JSON, front-matter style markdowns, database etc.)
  2. can render with any template engine (Twig, ejs, Pug, Mustache etc.)
  3. written in JS (preferably TypeScript)
  4. easy to extend with JS code
  5. supports incremental builds
  6. uses MVC pattern
  7. learning and using is easy (Gatsby, Hugo, Jekyll, Eleventy etc. are so cool but harder to learn and configure)

And because I wrote a ton of custom static generators before; I tought I can improve the concepts to a point where its (hopefully) useful for others.

This project is structured as a toolkit split to many packages, published under the @static-pages namespace on NPM. In most cases you should not use this core package directly, but the @static-pages/starter is a good point to begin with.

Where should I use this?

This project targets small and medium sized websites. The rendering process tries to be as fast as possible so its also useful when you need performance.

Usage

import fs from 'node:fs';
import path from 'node:path';
import staticPages from '@static-pages/core';

staticPages({
    from: [
        { title: 'About', url: 'about', content: 'About us content' },
        { title: 'Privacy', url: 'privacy', content: 'Privacy content' },
    ],
    controller(data) {
        data.now = new Date().toJSON();
        return data;
    },
    to({ title, url, content, now }) {
        const fileName = path.join('public', url + '.html');
        const fileContent = `<html><body><h1>${title}</h1><p>${content}</p><p>generated: ${now}</p></body></html>`;
        fs.mkdirSync(path.dirname(fileName), { recursive: true });
        fs.writeFileSync(fileName, fileContent);
    }
})
.catch(error => {
    console.error('Error:', error);
    console.error(error.stack);
});

Notes

The usage example above does a rough presentation only and not considered to be a production ready snippet. Helpers to read and write documents are provided in separate packages, eg. @static-pages/io.

Documentation

For detailed information, visit the project page.

staticPages(...routes: Route[]): Promise<void>

Each route consists of a from, to and a controller property matching the definition below.

interface Route<F, T> {
    from: Iterable<F> | AsyncIterable<F>;
    to(data: T): void | Promise<void>;
    controller?(data: F): undefined | T | Iterable<T> | AsyncIterable<T> | Promise<undefined | T | Iterable<T> | AsyncIterable<T>>;
}

The controller may return with multiple documents, each will be rendered as a separate page. Alternatively it may return undefined to prevent the rendering of the current document.

Missing a feature?

Create an issue describing your needs! If it fits the scope of the project I will implement it.