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

swc-helpers

v0.0.2

Published

Initial attempt at using swc to create a CRUD database that uses Typescript as it's storage, without further indexed storage.

Downloads

3

Readme

Initial attempt at using swc to create a CRUD database that uses Typescript as it's storage, without further indexed storage.

Given the speed of swc, this becomes a viable option, and this makes it possible to have a much faster and more stable typerepo!

Also refactors become way easier this way and potentially it can be de foundation of a new IDE that lets you do alterations (with or without AI) to a huge codebase in with high speed and reliability

Motivation:

  • good foundation for a framework for metacoding (code that writes code)
  • parse a statement dependency tree, file dependency tree, and operation dependency tree
  • simplify huge rewrites and refactors, e.g.:
    • changing a functionName everywhere in the codebase
    • moving statements around the codebase
  • make the migration to other programming languages or to other Javascript runtimes (e.g. bun.sh) easier
  • keep a strict convention of your code