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

recursive-proxy-handler

v1.1.1

Published

Recursively proxy objects values

Downloads

5

Readme

recursive-proxy-handler

Description

recursive-proxy-handler helps create a proxy object with attribute getters which return a proxy of the objects they would normally return.

This library simply decorates the given proxy handler so that it is easy to compose it with other "proxy-handler enhancers".

Usage

const { recursiveProxyHandler } = require('recursive-proxy-handler')

const handler = {
  get: (target, prop, receiver) => {
    console.log(`Get property "${prop}"`)
    return Reflect.get(target, prop, receiver)
  }
}

const recursiveHandler = recursiveProxyHandler(handler)
 
const obj = { b: { c: { d: 42 } } }

const a = new Proxy(obj, recursiveHandler)

const foo = a.b.c.d
// log: Get property "b"
// log: Get property "c"
// log: Get property "d"
// foo = 42

Details

This library aimes at providing a proxy object which will proxy any object extracted from it by any means.

Another way to expain this the aim of this library is the following:

Mary is the implementer of a JavaScript object "obj"
Bob wraps "obj" using this library and passes the wrapped object to Paul.
Paul can do whatever he wants with the object.

Bob has the means to intercept, modify or inspect any values passed from Mary to Paul through "obj".

This metaphor has its limits (Mary and Paul can use cryptography to avoid the "man in the middle attack" from Bob), but hopefully it helps convey the intent of this library.

A concrete usage of this library is to monitor all the effects that some code has on a given object. It can be useful to understand better what a given function does (eg. which properties of the input are read or modified).

This library could also be used to make an object deeply immutable.

Scenarios covered and tested

  • proxy values extracted with get()
  • proxy values extracted from apply()
  • proxy values extracted using a callback passed to apply()
  • proxy values extracted using a callback passed to set()
  • proxy values extracted from the constructor
  • proxy values extracted using a callback passed to the constructor
  • proxy all values returned by iterables
  • proxy value of 'this' in methods
  • proxy values extracted using a callback passed through defineProperty()
  • proxy values extracted from getOwnPropertyDescriptor()
  • proxy values extracted using a callback passed using the property descriptor setter
  • proxy values extracted from getOwnPropertyDescriptors()
  • proxy values extracted using a callback passed through property setters
  • proxy values extracted from getPrototypeOf()
  • proxy values extracted using a callback passed through setPrototypeOf()