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

chimpsky

v1.6.1

Published

a html publishing platform

Downloads

11

Readme

Chimpsky

A Markdown 2 HTML library by Toru Interactive

Setup

./guides/setup.md

Configuration

The following overrides can be set in the ./chimpsky.config.js in your project.

const paths = {
  "src" : "./src",
  "markdown" : "./docs",
  "menus" : "./docs/menus",
  "public" : "./public",
  "templates" : "./src/templates",
  "dist" : "./dist",
  "edit_base" : "https://gitlab.com/my-group/my-project/blob/master",
  "issues_url" : "https://gitlab.com/my-group/my-project/issues/new"
}

const metadata = {
  "template" : "default",
  "title" : "My Web Page" 
}

Usage

node build; # builds all files in one go
node watch; # watches `docs` and builds pages as they're edited
node watch-reload-templates; # same as watch but reloads templates. For chimpsy dev.

Developing

How to work on a local copy of chimpsky in your project. First clone your project into your Vagrant box...

  • make a /app/tmp folder in your vagrant box
  • make sure /tmp is .gitignored in your project
  • Clone chimpsky into /app/tmp/chimpsky

then npm link your local version of chimpsky to your project root...

vagrant ssh;
cd /app/tmp/chimpsky;
sudo npm link;
cd /app
sudo npm link chimpsky;

Then you can work on the files in your project's /tmp/chimpsky folder and run them directly from your project without publishing.

Publishing

change the version number in ./tmp/chimpsky/package.json & commit your change, then publish...

vagrant ssh;
cd /app/tmp/chimpsky;
npm adduser; # use Sean's NPM login
npm publish --access public;

goto chimpsky's NPM page to see if it's published. You should see your new version number on the right.