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

wsindex

v1.1.1

Published

A static site generator for a simple link list.

Downloads

42

Readme

wsindex v1.1.1

:vertical_traffic_light: A static site generator for a simple link list.

wsindex is a static site generator which creates the index web page of the list of web pages.

:cd: Install

Via npm:

npm i -g wsindex

or, if you prefer local install:

npm i wsindex

Why is this necessary?

If one uses many many static site generators in a project and invokes them simultaneously, then it's a mess to open all of them. This tool works as the index of all the pages and works as the portal of your many many generated static sites.

Usage

In package.json, define wsindex property:

package.json:

{
  ...
  "wsindex": {
    "pages": [
      {
        "title": "The title of the page",
        "desc": "The description of the page",
        "serve": "The url when being served",
        "build": "The url when being built"
      },
      ...
    ]
  }
}

Then hit command wsindex:

wsindex

This serves the single web page of the above link list.

Hit the command wsindex build:

wsindex build

This outputs the html under the build/ directory.

Config

The port number of the server and output directory are configurable.

Full configurations are like the below:

{
  "wsindex": {
    "port": 9000,
    "dest": "build",
    "pages": [
      "... list of object of links here ..."
    ]
  }
}
  • port is the port of the server.
  • dest is the destination directory when being built.
  • pages are the list of link entities.

License

MIT