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

chicago

v1.1.0

Published

A front-end JavaScript library for user-interface developers.

Downloads

29

Readme

#Chicago.js ##A front-end JavaScript library for user-interface developers.


###Intro

Chicago.js is a small, fast JavaScript library built specifically with front-end and user-experience developers in mind. Primarily, the library is a collection of useful utility and cross-browser support functions, allowing for quicker and easier development it fewer bugs and cross-browser/device issues.

Given that there are already a ton of JS libraries out there, I've created several goals for this project:

  • To be fast, lightweight, and easily deployable
  • To create and allow for a consistent cross-browser/device experience
  • To find real solutions for real problems - to not be repetitive
  • To be modular and extendable - creating a plugin for the library should be easy
  • To always be reliable through rigorous testing
  • To allow for easy contribution in the spirit of open-source software

Here are some links for quick reference:


###Dependensites

Note: Chicago.js is, for the time being, dependent on jQuery. Make sure to reference jQuery before you include Chicago.js in your project.


###Installation

Chicago.js can be installed several different ways:

####Manually:

  • Download the latest release from GitHub
  • Unzip the package
  • Copy dist/Chicago.js or dist/Chicago.min.js from the package into your project's folder
  • Reference the file in the footer of your HTML pages:
<script src="Chicago.js"></script>

####Using Bower

cd ~/your/project
bower install Chicago

####Using NPM

cd ~/your/project
npm install chicago

###Usage

How to use Chicago.js

Chicago.js creates an object on the window/global called Chicago. You can access this object and it's methods/properties by referencing the global object directly:

var myChicago = window.Chicago;

The recommended way to access the global Chicago object is by passing it as an argument of an anonymous closure:

;(function(_c) {

	// Now we can use _c to access Chicago...
	console.log( _c.version ); // will output 1.0.0

})(Chicago);

Learn more about anonymous closures and the module design pattern on MDN.


###API Docs

You can access all documentation from this link.

Chicago.js is broken down into modules. Each module contains it's own methods and properties. Below are links to the docs for each module: