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

ask-code-bot

v1.1.0

Published

Bot to manage questions in #ask-code

Downloads

5

Readme

Ask code bot

Bot to manage questions in #ask-code

Roadmap

  • [x] Exclude Qs asked last 24hrs

  • [x] Choose an avatar/theme and update the bot's tone accordingly, if needed.

  • [x] Put links of the unanswered questions in a thread to have less pollution in the main channel. Then in the main message output something like:

    ${unattendedCount ? "\n\n Link(s) to unattended questions in :thread:" : ""}

  • [x] Add test coverage for existing functionality

  • [x] Structure the code ~a bit~ much better

  • [x] Use a scheduler to run the report analysis everyday at 9am CET

  • [x] Mark workflow's questions as ✅ when the bot says it's done

  • [x] Deploy the bot somewhere (dcai_dev?)

  • [ ] automated Deployment process (look at what was done for CodeAgent)

  • [ ] Check which people respond/react to tickets and congratulate them in the report 🎉

  • [ ] Check commonly used emojis as ticket status and update code accordingly (example: people use :spinner: and :eyes: for "being looked" )

  • [ ] Identify issues (by following some conventions, like with msgs prefix) and assign a given issue to a member of a group. Example groups: tech, product, AI quality. A question with tech prefix can be assigned to member from Nebula/Pular team