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

private-name

v0.1.0

Published

Simple shim for ES.next Private Names

Downloads

11

Readme

name

A very simple ES.next shim. It works fairly well without any monkey-patching (though it does need to create one non-enumerable property on Object.prototype but it's much less intrusive than replacing functions. The variable name is random and uses unicode characters so the chances of conflicts are slim to none)

Installation

Install with component(1):

$ component install ilsken/name

Usage (with component or node.js)

var Name = require('name')
var myObject = {}
// you can also use new Name('something') to create a friendlier name for debugging tools which can see hidden properties

var hiddenProperty = new Name()

myObject[hiddenProperty] = 'foo'

console.log(myObject) // {}
console.log(myObject[hiddenProperty]) // "foo"
console.log(myObject.hasOwnProperty(hiddenProperty)) // false
console.log(Object.keys(myObject)) // []

## Usage (plain script tags)
```html
<script src="dist/name.js"></script>
<script>
  var hiddenProperty = new Name()
  // etc

Gotchas

While this shim for the most part works without any monkey-patching there are currently a couple ways to leak the private properties names. If you want to fix those leaks you can use the patches below

Object.propertyNames(object)

var props = Object.getOwnPropertyNames
function getOwnPropertyNames(obj){
	return props(obj).filter(Name.isPublic)
}
Object.getOwnPropertyNames = getOwnPropertyNames

Object.hasOwnProperty(Object.prototype, hiddenProperty)

If you define hidden properties on Object.prototype the method we use to hide doesn't work. I don't know why you would define hidden properties on the prototype but just in case here's how you'd patch this leak

var has = Object.hasOwnProperty
function hasOwnProperty(obj, prop){
	return Name.isPublic(prop) && has(obj, prop)
}

License

MIT