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

@lusito/mono-docs

v0.19.2

Published

A static documentation generator targeted at normal and monorepo code repositories.

Downloads

29

Readme

@lusito/mono-docs

A static documentation generator targeted at normal and monorepo code repositories.

I started this project since vuepress broke on newer node.js versions and I felt like tackling the issues I had with it.

Other code generators make your documentation source to feel a bit out of place. I'd like the documentation to feel as native to a code repository as possible. All documentation will stay in the respective projects directory structure and the configuration for it stays in yaml files. It was originally planned to stay in the front-matter, but since github shows front-matter when displaying markdown, this made everything too ugly.

I'm not sure yet if this will become a public tool, which can be adjusted to your liking or just a tool specific for my projects and design. In theory, it could be easily themeable, as I'm using JSX syntax via tsx-dom-ssr to generate the HTML. If you feel like this might be something for your projects, give me a heads up.

License

@lusito/mono-docs has been released under the MIT license, meaning you can use it free of charge, without strings attached in commercial and non-commercial projects. Credits are appreciated but not mandatory.