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

no-garbage

v1.0.0

Published

Tiny subset of JavaScript

Downloads

2

Readme

no-garbage stability

npm version build status test coverage downloads js-standard-style

Tiny performant subset of JavaScript. Combine with standard for best results.

Usage

$ no-garbage

Rules

  • all of ES3
  • most of ES5 (for now)
  • small selection of ES6 (const, fat arrow, template strings)
  • nothing from ES7

ES5 added functional extensions to built-in objects (e.g. Array.forEach). If the :: chaining syntax lands in JS, all ES5 built-in methods can be deprecated, as using external functions (e.g. from npm) will be just as convenient, breaking the TC39's monopoly on nice syntax.

E.g. no more odd unreadable nesting:

const reduce = require('reduce')
const root = require('root')
const map = require('map')

const arr = [ 1, 2, 3, 4 ]
const num = root(reduce(map(arr, (n) => n * n * 2), (t, n) => t + n, 0))

Weird multiline not-quite-lisp:

const reduce = require('reduce')
const root = require('root')
const map = require('map')

const arr = [ 1, 2, 3, 4 ]
const num = root(
  reduce(
    map(arr, (n) => n * n * 2),
  (t, n) => t + n, 0)
)

Or inconvenient placeholder names:

const reduce = require('reduce')
const root = require('root')
const map = require('map')

const arr = [ 1, 2, 3, 4 ]
const mapped = map(arr, (n) => n * n * 2))
const reduced = reduce(mapped, (t, n) => t + n, 0)
const num = root(reduced)

But instead we get nice things:

const reduce = require('reduce')
const root = require('root')
const map = require('map')

const num = [ 1, 2, 3, 4 ]
  ::map((n) => n * n * 2)
  ::reduce((t, n) => t + n, 0)
  ::root()

The less stuff we have to name, the better.

Rant

The TC39 seems to dislike JavaScript so they keep adding new semantics to change the core language. A full reboot so to speak. There's some of us that like JavaScript and would like to keep using it, even if engines support more stuff we didn't ask for. Nanoscript is a tiny, performant subset of JavaScript that doesn't deal with weird semantics (mostly). Have at it. Others might hate JS, but you don't have to hate it too.

Installation

$ npm install no-garbage

License

MIT