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

@laserware/arcade

v3.11.1

Published

Miscellaneous utility functions.

Downloads

670

Readme

Arcade

Miscellaneous utility functions. Check out the documentation site for available functions.

Overview

This is a collection of utility functions commonly used in other @laserware (and non-@laserware) projects. It's essentially a combination of "Diet Lodash", TypeScript helpers, and helper functions for performing certain tasks based on the execution environment (i.e. Node.js versus the browser).

Why don't use just use Lodash?

Lodash is super beefy. If you don't want to ship a lot of unused extra code, you have to use lodash-es. Most of Lodash's functions aren't needed anymore. You probably don't need Lodash.

Why did you vendor some libraries instead of just installing and re-exporting them?

To avoid constantly managing dependency updates. If a library is less than 100 lines of code, I'm going to just copy the code, give props, and include the license.

Why did you install and re-export some libraries?

For the same reason that I vendor them: to avoid constantly managing dependency updates for libraries that are used in several projects. I just need to update it here and publish a new version, then I only need to update one dependency (this one) in the affected projects.