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

babel-plugin-prototype-prop-define

v2.5.0

Published

Transform assignments to properties on built-in prototypes to Object.defineProperty calls

Downloads

23

Readme

babel-plugin-prototype-prop-define

A babel plugin for working around javascript's "override mistake" when dealing with frozen Primordials (built-ins).

transformation

If your primordials are frozen, such as in SES, assigning keys that are found on the prototype will throw an error.

Object.freeze(Object.prototype)

const x = {}
x.toString = () => 'hello'
// => TypeError: Cannot assign to read only property 'toString' of object '#<Object>'

Since this is a common, this plugin is provided to transform code into a safe form using Object.defineProperty:

Object.freeze(Object.prototype)

const x = {}
(function (parent, key, value) {
  Object.defineProperty(parent, key, {
    value: value,
    writable: true,
    enumerable: true,
    configurable: true
  })
  return value;
})(x, "toString", () => 'hello');
x.toString()
// => 'hello'

The code is transformed into an IIFE in order to ensure the "parent" (x), "key" (y) and "value" (() => 'hello') statements are evaluated exactly once, and that the whole expression resolves to the value of the "value" statement. This is needed because Object.defineProperty calls resolve to undefined.

For "computed" assignment, the resulting code is a little uglier.

const x = {};
const y = 'toString';

x[y] = () => 'hello'

becomes

const x = {};
const y = 'toString';

(function (parent, key, value) {
  ["constructor", "__defineGetter__", "__defineSetter__", "hasOwnProperty", "__lookupGetter__", "__lookupSetter__", "isPrototypeOf", "propertyIsEnumerable", "toString", "valueOf", "__proto__", "toLocaleString", "length", "concat", "find", "findIndex", "pop", "push", "shift", "unshift", "slice", "splice", "includes", "indexOf", "keys", "entries", "forEach", "filter", "map", "every", "some", "reduce", "reduceRight", "join", "reverse", "sort", "lastIndexOf", "copyWithin", "fill", "values", "name", "arguments", "caller", "apply", "bind", "call", "message"].includes(key) ? Object.defineProperty(parent, key, {
    value: value,
    writable: true,
    enumerable: true,
    configurable: true
  }) : parent[key] = value;
  return value;
})(x, y, () => true);

Here the check that is normally performed at parse time (checking if the key is in this whitelist), is performed at runtime to determine if normal assignment or Object.defineProperty should be used.