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

jtz-js-utils

v0.0.1

Published

Random utilities, WIP

Downloads

1

Readme

Tiny bits of code that I often reach for across projects.

Work in progress, use at your own risk, etc.

NodeJS Versions Supported

To ship ESM only, this supports Node V >= 12.17.0, since those versions support ESM imports out-of-the-box.

Build Setup

There are a few peculiarities worth noting about the build setup used here:

  • TypeScript
    • Config has libs set to include DOM in all TS files, not just those under src/web. This is slightly unsafe, as it won't catch me doing something silly like using document.location inside src/node/index.ts
      • I'm doing this because isolating libs to specific files is almost impossible with TypeScript at the moment - triple slash directives bleed into other files, and VSCode doesn't play nice with multiple root tsconfigs, so the only way to do this correctly would be to split each subdirectory into a completely isolated build and bundling step... still might be worth exploring at some point
  • Bundling
    • Using Rollup
    • Targeting UMD for browser, ESM for NodeJS (since most live versions support now)

Testing

Tests are ran using Ava, which can execute them in parallel.

Due to an issue with NodeJS ESM requiring file extensions to be included in import syntax - but this breaking TS-Node completely - I am running Ava against the transpiled JS (/dist) instead of the raw TypeScript source (which would require TS-Node).