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

qute-packages

v1.0.0

Published

It's a cute cli tool for font-end developers.

Downloads

2

Vulnerabilities

Powered byPowered by Snyk
  • 0High
  • 0Medium
  • 0Low

Links

Git

Maintainers

antfootantfoot

Keywords

Readme

What's this?

It's a cute cli tool for font-end developers.

It can help front-end engineers start project without configuring webpack or others.

For now, this tool focus on fe developing.

All Qute Orders

qute docsite-*

  • orders

    • qute docsite-serve [targetPath] [-m, --multi] [-i, --show-index]

      Lanch current directory as a website.

      • [-m, --multi]

        Each subdirectory will be lanched as a single website by default

      • [-i, --show-index]

        If dirname matches /^\d*-/, such as 0-README.md, the site will not show 0- but show README by default.

        If you want to show 0-, just add this param.

      • [targetPath]

        target directory. ./ by default.

    • qute docsite-push [branch] [-m, --multi] [-i, --show-index](beta and take care!)

      It will push current directory to github.

      • branch

        The target remote git branch. gh-pages by default.

      • [-m, --multi]

        Each subdirectory will be pushed as a single website by default.

      • [-i, --show-index]

        If dirname matches /^\d*-/, such as 0-README.md, the site will not show 0- but show README by default.

        If you want to show 0-, just add this param.

  • config files

    • .repo Tell docsite what is this project's repo
    • .sidebarshowignore files that should not be shown in sidebar (It will be reached by url)
    • .sidebarfileignore files that should not be created when creating docsite website (It will not be reached by url)
    • .navbarignore files that should not be shown in navbar
    • README.md project readme.
    • _sidebar.md user defined sidebar. Only work in default mode, not --multi mode
    • _navbar.md user defined navbar. Only work in default mode, not --multi mode

CHANGELOG

  • 1.0.1

    update readme

  • 1.0.0

    first publish

LICENSE

MIT