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

kolay

v2.1.2

Published

The runtime compiled documentation tool. Scale to any size with flat build cost.

Downloads

7,622

Readme

kolay

Documentation system for the the @universal-ember family of projects.

Features

Use Markdown

  • from any folder, any project (good for monorepos)
  • scales infinitely with your project size, as compiling the pages is done on-demand, rather than on-deploy
  • any codefence can become a live demo with the live tag
    Some prose here about the demo
    
    ```gjs live
    <template>
      interactive!
    </template>
    ```

Use JSDoc

  • JSDoc / TypeDoc is renderable via the <APIDocs /> component
    ## API Reference
    
    <APIDocs @package="my-library" @module="..." @name="theExport" />
  • render examples from your jsdoc for interactive demonstration of concepts using
    text here
    
    ```gjs live
    // the "live" tag on the codefence
    ```

Navigation

  • generate navigation based on convention based file layout