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

@customcommander/macgyver

v1.1.1

Published

Survival Kit For Broken Native Objects

Downloads

3

Readme

Build Status

MacGyver

Restore Native Prototypes To Their Full Glory

Installation

npm install @customcommander/macgyver

How it fits into your build or project is your own personal business but just know that it is an UMD module.

The Problem

People or libraries monkey patching native prototypes with broken custom implementations that break other people's code.

Example

Go to any website (with a decent browser), open the console and run this:

[1,2,3].reduce((tot, num) => tot + num, 0);
// 6 (Yay!)

Now find one using Prototype 1.6.0.2 (for instance) and run the same line:

[1,2,3].reduce((tot, num) => tot + num, 0);
// [1,2,3] (WTF?!)

If you know where to look you can immediately see the issue:

Array.prototype.reduce.toString();
// "function () {
//     return this.length > 1 ? this : this[0];
// }"

The Workaround Solution

Go to that same website using Prototype 1.6.0.2, drop MacGyver in the console and then run:

macgyver([1,2,3]).reduce((tot, num) => tot + num, 0);
// 6 (Yay!)

macgyver([1,2,3]).reduce.toString();
// "function reduce() { [native code] }"

Array.prototype.reduce.toString();
// "function () {
//     return this.length > 1 ? this : this[0];
// }"

What MacGyver did was to simply recreate your array using pristine native methods from a separate frame.

The Permanent Solution

If you would rather not wrap your objects in some duct tape all the time, you can duct tape the current context permanently instead:

macgyver.ductTape();
Array.prototype.reduce.toString();
// "function reduce() { [native code] }"

The Future

MacGyver only deals with arrays for now. If you need more from it just ask, or better: raise a pull request.