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

@webreflection/empty

v1.0.0

Published

Just various empty and frozen references

Downloads

328

Readme

@webreflection/empty

Social Media Photo by Adlan on Unsplash

This is basically the same as empty except it's a dual module and it doesn't care about freezing callbacks (for better or worse) but it does freeze other references, such as array or object, and even in production, where IMHO it matters most.

import {
  args,                   // (...args) => args
  arguments as Arguments, // function arguments
  array,                  // Object.freeze([])
  context,                // function context
  false as False,         // () => false
  function as noop,       // () => {}
  identity,               // any => any
  object,                 // Object.freeze({})
  string as str,          // ''
  true as True            // () => true
} from '@webreflection/empty';

isolated exports

Each utility can be imported directly without bloating the outcome:

import args from '@webreflection/empty/args';
import arguments as Arguments from '@webreflection/empty/arguments';
import array from '@webreflection/empty/array';
import context from '@webreflection/empty/context';
import false as False from '@webreflection/empty/false';
import function as noop from '@webreflection/empty/function';
import identity from '@webreflection/empty/identity';
import object from '@webreflection/empty/object';
import string as str from '@webreflection/empty/string';
import true as True from '@webreflection/empty/true';

... but why?

I use one of these utilities all over the place in my projects so I've decided that this approch would work better.