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

manual-filetree

v0.0.1-rc.12

Published

A filetree display from a manual configuration.

Downloads

3

Readme

filetree

A filetree view from yaml config.

Example:

Input:

- dir1:
  - file.txt
- dir2:
  - subdir:
    - otherfile.txt

Output:

.
├── dir1
│   └── file.txt
└── dir2
    └── subdir
        └── otherfile.txt

publishing

Publish the crate with cargo-release. When this created tag is pushed, it should trigger the CD pipeline. This will build the npm package and publish it to the forgejo package repository as well as create a release on the Codeberg repo.

releases

To build a wasm release, run wasm-pack build --target web.

manual testing

Follow the instructions to build a release. Then run a little HTTP server (like python -m http.server) so you can test it in the browser.