is-weakmap-polyfill

npmpackage.info

Gathering detailed insights and metrics for is-weakmap-polyfill

Other packages similar to is-weakmap-polyfill

global-map-set-polyfill

0.0.2

Ensures the polyfill implementation is used for ES6 `Map`, `Set`, `WeakMap`, and `WeakSet`.

@teamteanpm2024/inventore-doloremque-voluptas

1.0.6

[![github actions][actions-image]][actions-url] [![coverage][codecov-image]][codecov-url] [![dependency status][deps-svg]][deps-url] [![dev dependency status][dev-deps-svg]][dev-deps-url] [![License][license-image]][license-url] [![Downloads][downloads-im

@taktikorg/unde-animi-omnis

5.8.117

<p align="center"> <a href="https://www.npmjs.com/package/@taktikorg/unde-animi-omnis"><img src="https://img.shields.io/npm/v/@taktikorg/unde-animi-omnis"></a> <a href=""><img src="https://img.shields.io/github/actions/workflow/status/RemiMyrset/@taktikor

@womorg/porro-impedit-suscipit

4.8.120

![npm](https://img.shields.io/npm/dm/data-structure-typed) ![GitHub contributors](https://img.shields.io/github/contributors/womorg/porro-impedit-suscipit) ![npm package minimized gzipped size (select exports)](https://img.shields.io/bundlejs/size/data-st

Why another shim?

Mainly because the most feature complete one added random properties to any object you used with it per weakmap you used it with. This does bad things for optimization since after a certain number of added properties v8 gives up and puts your object into slow hash-table mode. ilsken/weakmap stores all it's data for under one property (each weakmap then gets a key on this property, since it won't effect the optimization of the parent object).

On top of that this one is only 40 lines and it's pretty easy to understand what's going on. I also kept any funny buisiness like monkey patching out of it

Differences from Benvie/WeakMap

Faster, slimmer, easier to read code (just 40 lines!)

All WeakMaps data store under one property on the key, easier to debug/delete

No monkey patching: This can be a good or a bad thing. Good news is it leaves native functions untouched and everything is less complicated and runs smoother. Bad news is you can get access to the weakmap data via getOwnPropertyNames but this is javascript so if you're trying really hard to break stuff who am I to stop you?

Assumes ES5, if your enviorment doesn't support Object.defineProperty you are expected to provide the appropriate polyfills

Differences from raynos/weakmap-shim

No monkey matching (weakmap-shim patches valueOf and will break if you change it on an object that is used in a weakmap, though it does get rid of the ugly property name problem)

Slightly smaller but really it's about 300 bytes difference, nothing to write home about

Probably faster due to less closures being involved but I'm lazy to benchmark. In essence it does the same thing as Benvie/WeakMap and raynos says in his readme that method is faster so let's go with that

npmpackage.info

Other packages similar to is-weakmap-polyfill

Installations

Developer Guide

No

CommonJS

6.11.1

3.10.10

Score

Releases

Unable to fetch releases

Contributors

Download Statistics

Bundle Size

814.00 B

395.00 B

Maintainers

Package Meta Information

Total Downloads

1,462

Daily Downloads

Weekly Downloads

Monthly Downloads

Yearly Downloads

weakmap

Why another shim?

Differences from Benvie/WeakMap

Differences from raynos/weakmap-shim

TODO: