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

indieweb

v0.0.1-dev.1

Published

A JavaScript library (and runnable server/process) for hosting your own [#indieweb](http://indiewebcamp.com/).

Downloads

6

Readme

indieweb

A JavaScript library (and runnable server/process) for hosting your own #indieweb.

What is an indieweb?

Great question. That has an evolving answer.

Currently

  • Serve HTTP at the / route

Future

Run it

make server

Restart on file changes with make watch.

Configuration

Configuration is accomplished with both config files (in ./config) and environment variables. Environment Variables have a higher priority.

Configuration defaults are loaded from defaults.json.

Accepted configuration parameters:

  • indieweb - General settings that are passed to all modules
    • .domain - Public domain of your indieweb
    • .me - A JSON Object describing the owner of this site. Currently this uses a JSON-LD Serialization of an AS Person.
  • indieweb-home - Settings for the homepage module
    • .title - Title of the page
  • DEBUG - Exactly as described in debug README. DEBUG=* to show all logs.
  • config - Path to config file other than defaults.json. config=/path/to/config.json make server
  • PORT - Port to listen for HTTP traffic on
  • findPortBase - If no PORT, portfinder will start at this port and look 1 by 1 to find an open port

Use in another webapp

If you prefer, you can use indieweb as a library.

Install with npm install --save indieweb.

Use like any other express app.

  • TODO: easily interop with other patterns like koa
const yourApp = require('express')();
const indiewebConfig = {};
yourApp.use('/indieweb', require('indieweb')(indiewebConfig))

Want a feature?

File an issue