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

robot-ninja

v0.0.2

Published

More than just an extensible wiki engine written in Node.js

Downloads

6

Readme

robot-ninja

More than just an extensible wiki engine written in Node.js

Design Goals

  • Create an extensible wiki middleware for koa
  • Be part of an application, not the entire application
  • Be the backend API, not the frontend
  • Code over configuration - store a code file that exports global configuration options and still allow individual options to be changed per page using the API
  • Use GitHub flavored markdown, but make it possible to use something else too
  • Support multiple storage backends starting with a git repository for storage
  • Support attachments, including large attachments
  • Provide standard wiki features like red links, versioning, comparision and change reversal (reverting)
  • Do not handle authentication, store access control and author information
  • Be servable from any base URL and otherwise provide a consistent API URL structure
  • Be RESTful and adhere to web standards (appropriate request methods and status codes)
  • Serve JSON data using the http://jsonapi.org/ specification
  • Have a client library available for this API (may be a separate repo)