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 🙏

© 2026 – Pkg Stats / Ryan Hefner

chronicles_of_angular

v0.6.0

Published

Wigy's collection of useful utilities for AngularJS.

Readme

Wigy's Chronicles of Angular

Wigy's collection of useful code pieces for AngularJS.

License

Copyright (c) 2015 Tommi Ronkainen Licensed under the GPL-2.0 license.

Release History

  • v0.6.0
    • Data persistence interface coa.store with in-memory implementation.
  • v0.5.4
    • Use new neat-dump instead of own implementation of d().
  • v0.5.3
    • TypeAny to allow any non-undefined value.
  • v0.5.2
    • TypeTuple providing options types defining list of element types.
    • Sub-classes TypePair and TypeTriple of TypeTuple.
    • Override better defaults {} and [] for TypeDict and TypeList.
  • v0.5.1
    • Fix prototype of TypeOptions.
  • v0.5.0
    • Add class name as a part of each prototype.
    • Support Type instance initialization directly from the constructor.
    • Change the Data initialization pattern to use Type instances.
    • New TypeList to contain instances of some defined other type.
    • New TypeDict as generic object container.
    • New TypeOptions to contain options with validation.
  • v0.4.2
    • Fix invalid reference in TimeStr.diff().
  • v0.4.1
    • Fix distribution files and version number.
  • v0.4.0
    • Update API docs to use ngdocs.
    • Implement type system with few types: boolean, string, integer and object.
    • Data and option validation.
    • Generic Data instance factory.
  • v0.3.0
    • Support fully Chronicles of Grunt build system.
    • Documentation for existing code.
    • New d() dump utility and audio player.
    • keyHandler directive.

Next Version

Done

Not Yet Done

Future Ideas

  • Data persistence engine for mongodb.
  • Data persistence engine for rest-api.
  • Deletion instances from storage.
  • Another storage API call calc() simimilar to find() which allows selecting fields in MongoDB-style.
  • Return value for update() similar to MongoDB.
  • Builder task for collecting data from JSON-files and setting up in-memory storage for single-file application (use CoG build).
  • Use https://github.com/kofrasa/mingo/ if installed, when parsing search filters.
  • Rendering for every class with member html(context), where context is RenderingContext instance (to be defined).
  • Page structure descriped by page.json files in the configured project directory tree.
  • Builder task for pages in single file application (use CoG build).
  • Application configuration mechanism to provide different settings for production and developement.