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

mukco-gpterminal

v0.0.15

Published

An attempt at faster terminal debugging using ChatGPT.

Downloads

50

Readme

GPTerminal

Faster debugging with ChatGPT.

Install Bun

curl -fsSL https://bun.sh/install | bash

Add OpenAI API Key

export OPEN_AI_API_TOKEN=your_token

Run failed command

➜  ~ npm run foo

# Error
pm ERR!  code ENOENT
npm ERR! syscall open
npm ERR! path /Users/foo/package.json
npm ERR! errno -2
npm ERR! enoent ENOENT: no such file or directory, open '/Users/foo/package.json'
npm ERR! enoent This is related to npm not being able to find a file.
npm ERR! enoent

npm ERR! A complete log of this run can be found in:
npm ERR! /Users/foo/.npm/_logs/2023-10-29T20_27_47_598Z-debug-0.log

Run gpterm

➜  ~ gpterm
The last command was: npm run foo.

## Are you sure that is the one you want to debug? (Y/n)

Y
Debugging npm run foo


# Debugger's response:

 This error typically occurs when there is no package.json file in your current directory. Please ensure that a package.json file exists in your project directory and you're located in the project root directory when running commands. If no package.json exists in your project you can create one with the npm init command.


# Code snippet:

 npm init -y


Debugger marked npm init -y as executable. Do you want to run it? (Y/n)

n