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

protojs

v1.0.6

Published

ES5 object manipulation library for node and modern browsers

Downloads

6,519

Readme

proto

ES5-compatible object manipulation library for node and modern browsers

Build Status npm version Code Climate Test Coverage

Documentation: http://milojs.github.io/proto/

Why not use underscore or lo-dash

  1. They do NOT use properties that are non-enumerable when they extend/clone/etc.
  2. They DO use enumerable properties from prototypes when they extend/clone/etc.
  3. When they clone, they create instances of Object rather than of the same class as cloned object.
  4. They implement many methods that are already implemented natively.
  5. They don't implement methods for inheritance and extention of prototypes.
  6. They create confusion when you read code as you can't clearly differentiate between arrays and objects (maps), e.g. when each function is used.
  7. Underscore has clumbersome chaining syntax, chaining in proto is more succinct.

Install

npm install mol-proto --save

To use and develop:

git clone [email protected]:milojs/proto.git
cd proto
npm link
cd ../<your project>
npm link mol-proto

Use

Node/browserify:

var _ = require('mol-proto');

Browser:

All functions are exported as properties of a global _ object when used with milo, there is no separate proto bundle yet (will be added shortly).

Functions