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

repr.js

v0.1.0

Published

Function similar to Python's repr or Ruby's Object#inspect.

Downloads

7

Readme

repr.js

Sick of 99% of objects in your runtime being represented as [object Object]? I sure am. repr takes a leaf out of python's book, and gives some identity to your objects so you can tell what they are without jumping through hoops.

It adds two global methods:

  • str(obj): print out a summary of obj
  • repr(obj): print out a more detailed representation of obj (similar to inspect() in ruby, and obviously repr in python)

It also overrides Object.toString() to use str, because that way you'll suddenly get useful information throughout your app in code that you don't necessarily control - in error messages, exceptions, and whenever you concatenate strings together. Note that you should never rely on the format of this (or any) toString() behaviour unless you specifically override it - the default implementation of Object.toString() is purely for informational purposes.

Here's some examples:

function Foo() {
  this.x = "123";
}
var f = new Foo();
f.complex = {a: 123, b:456};
f.fun = function() { };


>>> str(null)
(null)
>>> str(undefined)
(undefined)
>>> str([1,2,3])
[1, 2, 3]
>>> str({})
{}
>>> repr({a:"b"})
{"a": "b"}
>>> str(f)
<# object Foo>
>>> repr(f)
<# Foo; x: 123, complex: {"a":123,"b":456}, fun: (anonymous function)>
>>> repr(Foo)
function Foo() {
  this.x = "123";
}
>>> str(Foo)
(function Foo)
>>> str([1,f,3])
[1, <# object Foo>, 3]
>>> repr([1,f,3])
[1, <# Foo; x: 123, complex: {"a":123,"b":456}, fun: (anonymous function)>, 3]
>>> repr("foo\" bar")
"foo\" bar"

The code ends up dealing with a lot of edge cases, because javascript's type system is somewhat laden with traps. So please report any issues you find, and I'll endeavor to fix them as they come up.

Usage:

In the browser, you need only load it with a <script> tag. In node.js, you must require() it. You can either use the returned module's repr and str functions individually, or call the module's install method passing in the global object in order to install these same functions into the global scope.