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

docsense

v0.4.1

Published

An Intelligent Doc Generator tailored for EcmaScript Modules

Downloads

6

Readme

Docsense

Docsense is a pluggable and customizable AST to documentation generator which parses ECMASCIPT 2015+ using Babylon,

🤖 **It is still in early development, but operational! ** 🤖

Quick start

# Add with yarn
yarn add docsense
# Run init to create the default config file
yarn docsense init
# Run build to see your docs!
yarn docsense build

More info about CLI

Development

:muscle: Clone the project, then run yarn to install all dependencies.

git clone https://github.com/MattMcFarland/docsense
yarn

Scripts

There are a number of scripts that may be run using yarn - the ones that should work independent of developer environments are as follows:


| Command | Description | | ------------ | ------------------- | | yarn test | Runs all unit tests | | yarn build | Compiles source | | yarn docs | Runs the compiled code against this project | | yarn dev-docs | Watches src/generator for changes, building the new documentation on changes. This will not work unless docs have already been built first. |

Debugging

This project may be debugged with VSCode, and has not been tested with other IDEs. You can set breakpoints within the source code, press F5 and run. The debug mode will basically run docs against this project, generating the db.json (and eventually the docs) as if you were to run docsense against this project in production.

Architecture

Docsense will eventualy run in the command line against the process.cwd() of the project a user has it installed in as a module. As of now, it only runs against this project, parsing all of the code, then creating a database which may be queried by the document generator. The document generator is currently unfinished, so after running yarn docs - you may run yarn dev-docs which will runs a local server that hosts the generated documentation, updating automatically as you make changes to the generator scripts found in src/generator

Execution ->
  Read .docsenserc Config ->
    Generate AST ->
      Execute all plugins ->
        Plugin visitors create a database ->
          Static Docs are generated

LICENSE

MIT