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

vengeful-god

v2.0.0

Published

Angrily disable bad JS behavior, be sure to load polyfills prior to this...

Downloads

8

Readme

Are you paranoid, do you want some slightly saner rules for JS?

Do you wish to punish those who do not have sane type coercion going on? Do you wish to punish those who try to use eval locally?

Well this is the globally monkey-punching module for you!

  • The global object is frozen. No accidental globals allowed.
  • eval will only run in the global scope, implicit returns still work
  • Function will only accept a single argument, use arguments instead of named parameters if you use Function
  • No type coercion for builtin types, use String() / Number() instead.
  • .valueOf during coercion or Number() will not be allowed to return NaN.
  • .valueOf must return a string or number during coercion.
  • .toString must return a string during coercion.
  • Somewhat informative messages on failed coercion
  • Object.prototype is set to not have any properties
  • Builtin prototypes are frozen, as are constructors
  • throws on Object.setPrototypeOf()
  • throws on .__proto__
  • throws on Boolean, Number, and String constructors from creating object wrappers (new Boolean), allows extend still
  • throws on Boolean, Number, and String constructors odd behavior for ctor.call(primitive), ctor(), and ctor(more, than, one, arg)