Open Source Dashboard (for js developers)

Search for a command to run...

No comments yet. Be the first to comment.
When developing serverless functions and an API on AWS cloud platform, you also create an open API definition (swagger documentation), to download the file easily from the command line you can use tools like aws-cli or npm package. OK! so now what? w...
Your team has 14 versions of the same code review skill across 5 repos, with no way to sync them. when one improves, the others don't. drop a folder in .claude/skills/ and pray nothing drifts. source

AI agents are unreasonably good at writing SQL. They get specific error messages, fix their own mistakes in one retry, and can introspect query performance with EXPLAIN ANALYZE before you even ask. No

n8n has over 400 integrations. Zapier claims 7,000+. Every single one was hand-built, tested against a moving API, and will eventually break when that API ships a v2. The entire workflow automation in

Part of the "Your Next Startup" series, where I break down startup ideas I think are worth building. Auth0 sold for \(6.5B. Okta is worth \)15B+. CyberArk, Delinea, BeyondTrust, all printing money fro

For as long as software has existed, we've been building two doors into our systems. Door one: the UI, a carefully designed surface where humans point, click, and occasionally rage-quit. Door two: the

Javascript open-source maintainers often have a hard time tracking their npm package status.
I used until recently npm-stats.com to get npm information about my packages, recently the site stops to work, so as a coder it was an easy decision to start working on a clone.
The package I created is called npmdash. (short for npm dashboard)

The homepage is a very simple input field to enter the npm username. (be patient it can take a while.)

This is the packages view it's a list of the packages sorted by monthly downloads, including data on the package that can help you get more insight into the package, in the future more relevant data will be added.
You can use the hosted version, the docker version or the open-source CLI option.
The hosted version uses AWS fargate, you can clone the repo and build your docker version if needed, and deploy it to your own container solution.
CLI Usage
npm i -g npmdash
npmdash // will open the homepage
npmdash -u <username> // will open the packafes view for this username
Docker Usage
docker pull niradler/npmdash
docker container run -p 8989:8989 npmdash
For future improvements, I will like to improve the GitHub integration, improve the UI and get reports maybe? Still thinking about it.
Enjoy and let me know what you think :)