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

cc-toolkit

v0.1.3

Published

## Get started - yarn add https://bitbucket.org/trillitech/toolkit.git -save OR npm i https://bitbucket.org/trillitech/toolkit.git -save - Include js modules using cc-toolkit/js/[module-name]. Using AMD would look like

Downloads

3

Readme

Crescendo Toolkit [cc-toolkit]

Get started

  • yarn add https://bitbucket.org/trillitech/toolkit.git -save OR npm i https://bitbucket.org/trillitech/toolkit.git -save
  • Include js modules using cc-toolkit/js/[module-name]. Using AMD would look like
#!javascript
define(['cc-toolkit/js/page'], function(){})
  • Include scss modules using ~cc-toolkit/scss/[module-name].
#!scss
@import '~cc-toolkit/scss/form';

Tools

  • node
  • yarn
  • gulp
  • webpack

TODO

  • base file (main file / imports )
  • variables
  • forms
  • buttons
  • type ( fonts )
  • reset
  • grid

Recommended modules for your needs

  • jquery : https://www.npmjs.com/package/jquery
  • js-cookie : https://www.npmjs.com/package/js-cookie - working with cookies
  • ismobilejs : https://www.npmjs.com/package/ismobilejs - mobile testing
  • store2 : https://www.npmjs.com/package/store2 - Local/Session storage
  • google-maps : https://www.npmjs.com/package/google-maps - Async loading of google maps
  • extend : https://www.npmjs.com/package/extend - object extend

untested

  • urljs - get and set hash variables : https://www.npmjs.com/package/urljs
  • slugify2 : https://www.npmjs.com/package/slugify2

Development

To develop you will need to clone this repo and https://bitbucket.org/trillitech/frontend-toolkit. The then make a yarn link of the local cc-toolkit repo to use in the frontend-toolkit repo. Steps to do this.

#!terminal
$ git clone [email protected]:trillitech/toolkit.git
$ cd toolkit
$ yarn
$ gulp
$ yarn link
$ cd ../
$ hg clone https://bitbucket.org/trillitech/frontend-toolkit
$ cd frontend-toolkit
$ yarn
$ yarn link cc-toolkit
$ gulp ( or gulp server )