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

@millino/naked-ssg

v0.0.7

Published

Super-minimal, (almost) no deps NodeJS static site generator with i18n support.

Downloads

8

Readme

Yet another TypeScript SSG

But with built-in i18n support and a minimal API.

Why

No need for bloated code for simple tasks. We need to reduce over-engineering and keep our toolchains slim.

Usage

Initialize a project:

mkdir project-name
cd project-name
npx @millino/naked-ssg initialize

Some files need to be created manually, see the sections below.

To build the project:

npx @millino/naked-ssg build

todo:

npx naked-ssg server

Project structure

/
 - config.js
 - /pages
   - index.js
   - /test-sub-directory
     - index.js

Example config.js

import { SiteConfiguration, TranslationsMap } from "@millino/naked-ssg";

const CONFIG: SiteConfiguration = {
  cultures: ["it", "en"], // "it" is the default culture,

  // @todo:
  defaultCultureDirectoryBuildBehavior: "both", // Builds pages for both / and /it
};

const TRANSLATIONS: TranslationsMap = {
  it: {
    test: "Test IT",
  },
  en: {
    test: "Test EN",
  },
};

export { CONFIG, TRANSLATIONS };

Please note: The first culture in the CONFIG.cultures array will be the default culture, which currently has no dedicated subdirectory.

Example page

A page must have a default export, which is a function returning a string with the page markup.

/pages/index.js

import { TRANSLATIONS } from "../config.js";

const Index = (cultureCode) => /*jsx*/ `
<p>
    ${TRANSLATIONS[cultureCode].test}! ${2 + 2}
</p>
`;

export default Index;

The comment below is used to trigger the es6-string-jsx VSCode plugin functionality, which provides JSX-like syntax highlighting within the function body.

/*jsx*/

Page-level configuration

Certain specific behaviors are obtainable by exporting a localConfig constant. See the available configuration options in the example below:

import { TRANSLATIONS } from "../../config.js";

const Index = (cultureCode) => /*jsx*/ `
<p>
    ${TRANSLATIONS[cultureCode].test}! ${2 + 2}
</p>
`;

export const localConfig = {
  title: "Title", // The title tag
  skipForCultures: ["it"], // The current page won't be built for the "it" culture,
};

export default Index;

Plug-ins

Advanced features are OSP, meaning: plug-in system WIP, meanwhile fork the project.

Contributing

Pull requests are welcome. For major changes, please open an issue first to discuss what you would like to change.

Tests are more than welcome.