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

purejs

v4.0.23

Published

Purejs is an API to help create constructors and manage their prototype chain.

Downloads

38

Readme

Overview

Pure.js is an API to help create constructors and manage their prototype chain. Pure.js adheres to JavaScript's prototypal nature without introducing new ideas, allowing a greater integration with builtin constructors.

Installation

npm install purejs

Or using bower

bower install purejs

Bower

To use the component you will have to bundle the component using a tool like Browserify. For example:

./public/modules/app.js:

var pure = require('purejs')
console.log(typeof pure)

command line:

browserify -t debowerify ./public/modules/app.js > ./public/app.max.js

Testing

If you want to run the tests then you will need to do the following:

cd purejs
npm install
npm test

API

See purejs.org for the API reference and more info.

Changelog

4.0.23

  • Update constructor-kit to version 0.1.0

4.0.2

  • Refactor the build process to use Gulp
  • Added Coffeelint to the build process
  • Set main file in bower.json to be NPM module pure.js
  • Require bower consumers to use a tool like Browserify to bundle the module

4.0.0

  • Port source code to be CoffeeScript based
  • Replace constructor.create with constructor-kit function; API is identical to constructor-kit
  • Revamp the build process to use browserify and minify
  • Support UMD module definition
  • Deprecate the following features on constructors: copy constructors, init(), calling constructors without new, setting a name on a constructor
  • Register as a bower component and NPM module

3.0.0

  • Remove dependency on xport since it's deprecated.
  • Clean up the dev dependencies, making it much easier to test.
  • Create make files for minifying and testing.
  • Change the exported name in browsers to Pure instead of PURE.
  • isArray() no longer tests for Array-like objects. Objects are only considered an Array if they have Array in their prototype chain.
  • isObject() now uses the following test: o === Object(o).
  • add isPrimitive() to test for string, number and boolean literals.
  • add create() to create new objects from existing ones.
  • constructor.create: - remove the getName() method on constructors created via Pure.constructor.create(). - In a previous version the name argument was not being used, now it's being used by overriding the created constructor's toString() method. - The name argument no longer defaults to UnnamedConstructor. - If no name argument is given then the created constructor's toString() method is not overridden.
  • Change the unit tests to use Jasmine.