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

@nhevia/simple-docs

v0.6.5

Published

"Simple documentation tool"

Downloads

1

Readme

GitHub package.json version CircleCI Build Status Known Vulnerabilities PR GitHub Twitter Follow

simple-docs

A simple documentation tool.

Installation

npm install --save-dev @nhevia/simple-docs

Usage

  • Add sdoc as a package.json script:
"scripts": {
  "docs": "sdoc"
}
  • Use a comment block at the start of any file with sdoc preffix:
/*sdoc
This is the main component
*/

// your code
  • Run npm run docs. It will indentify documentation blocks in your project and generates an output file (sdoc.md by default, on root folder):

Since the generated file is markdown, it is supported inside documentation blocks.

/*sdoc
  This is the **main** component
*/

image

Options

  • -f <filename>, --file <filename>
    Set the output file name: sdoc -f docs-components | sdoc --file docs-components
  • -ni, --no-index
    Set the output file name. sdoc -ni | sdoc --no-index

Why?

Most major documentation libraries have tools that are beyond the current necessities for personal projects.

I needed a really simple tool to generate documentation for my scripts. Insert a comment block at the beggining of the file describing it and its usage and that's it.

Note that if you're working in a team with multiple people, there are better, more tested and reliable alternatives.

Contributing

Pull requests are more than welcome.

License

Copyright © 2020 Nicolas Hevia This project is MIT licensed