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

internal-prop

v4.0.9

Published

Gives access to native objects internal properties, such as proxy's [[Target]] and [[Handler]]

Downloads

22

Readme

internal-prop

Gives access to native objects internal properties, such as a proxy's [[Target]] or [[Handler]] or the private fields of an object

Warning

This module is native, it means that it contains c++ code that gets compiled every time the module is installed to ensure that the binaries can be read by your machine, the problem is that node apparently uses external tools that may be not present in your machine. If you don't have the necessary to compile the binaries npm should tell you what you need too do to achieve that. If the compilation fails regardless try deleting the node-gyp cache folder (Located at %LocalAppData%\node-gyp on windows)

Usage

The module gives you indipendent functions that you can use to extract internal properties of objects

import { getProxyData, getPromiseData, getOwnPrivateSymbols, getPrivateSymbolsProxy } from "internal-prop";

Supported

getProxyData()

If the provided value is a Proxy, it returns an object containing the target and the handler, otherwise it returns null

getPromiseData()

If the provided value is a Promise, it returns an object (PromiseResult) containing the state and the eventual result, otherwise it returns null. The returned state can be:

  • pending (0): The result will be null
  • fulfilled (1): The result of the Promise
  • rejected (2): The result will be the error that occurred

getOwnPrivateSymbols()

If the provided value is an Object, it returns an array containing the private keys in the object (They are a special kind of symbols)

getPrivateSymbolsProxy()

Creates an object containing a property for each private symbol of the passed object. You can use the function like this:

import { getPrivateSymbolsProxy } from "internal-prop";

class Class { #field = 1; get() { return this.#field; } }

const inst = new Class();
const priv = getPrivateSymbolsProxy(inst);
console.log(priv.field, inst.get()); // → 1 1
priv.field = 3;
console.log(priv.field, inst.get()); // → 3 3

But doesn't it break encapsulation?