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

cleandocs

v0.0.4

Published

Merge code and markdown files to create project documentation

Downloads

12

Readme

cleandocs

Merge code and markdown files to create project documentation.

This project is in very early alpha stage. It does the bare minimum to allow me to start writing literate coffee script in a way that doesn't clutter up the source code while I'm working on it. Expect plenty of changes as I get some free time to make them.

Getting Started

There are two ways to use cleandocs.

Grunt Plugin

This is the easiest and recommended way to use cleandocs when documenting a project. For examples and usage, see grunt-cleandocs

Command Line

The app also exists as a simple command line app.

Install the module with: npm install -g cleandocs Copy the example cleandocs.json file into the root directory of your project. Edit the dirs list to point to your src files, doc files, and output directory for each source directory you wish to document (Usually its just src and test).

Then from the same directory as the cleandocs.json file, type cleandocs. The files should be merged and output into the directory specified in the json config file.

If the {docco: true} option is set, the files will also be passed through docco and converted into HTML files. Directory structure is preserved.

Examples

For an example of using cleandocs from the grunt plugin, see grunt-cleandocs.

This project is an example of cleandocs working from the command line.

First install cleandocs

npm install -g cleandocs

Then clone this repository and clean out the existing docs folder

git clone https://github.com/niels4/cleandocs cd cleandocs rm -rf out/docs

Then run clean docs and verify that the literate coffeescript files were generated

cleandocs
ls out/docs/src

Future plans

  • Expand the documentation using cleandocs
  • Create a searchable table of contents page based off of the files created
  • Export documentation as static site at the end of the grunt build task

License

Copyright (c) 2013 Niels Nielsen. Licensed under the MIT license.