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

generator-smokegen

v0.2.1

Published

Yeoman generator for complex multi-sub-project AngularJS projects.

Downloads

7

Readme

common module

This project uses bower (via node, git) gulp (via node), compass (via ruby), and karma (via node) for building and testing.

Ensure git is installed and git is in your path, to test 'git --version' in a terminal. Ensure node and npm are installed (http://nodejs.org/), to test 'node -v', 'npm -v' in a terminal. Ensure ruby 1.9.x is installed (http://rubyinstaller.org/downloads/), make sure you choose the option to add to the path. Ensure ruby and gem are in your path env variable (probably C:\Ruby193\bin), to test 'ruby -v', 'gem -v' in a terminal. Ensure compass is installed (http://compass-style.org/install/), to test 'compass -v' in a terminal.

If you are behind a firewall and can't access git:// urls you may need to run the following command: git config --global url.https://github.com/.insteadOf git://github.com/

Ensure gulp, bower, karma-cli are installed globally. npm install -g bower gulp karma-cli

Install the project (probably done by yeoman): npm install bower install

Build the project: gulp build (or) gulp

Run the tests: gulp test

Serve the project locally (http:\localhost:9001): gulp serve

Build the distribution: gulp dist

Serve the distribution locally (http:\localhost:9001): gulp serve-dist

To autowire in new bower components

gulp wiredep

To autowire in YOUR js and scss files

gulp wireapp

The distribution contains (at least): index.html : for the demo scripts/ : for the project and vendor scripts styles/ : for the project and vendor css sass/ : for the project sass fonts/ : for the fontawesome fonts

All these need to be present for the the distribution to be demo'ed in a browser, but it is suggested that not all these be included in projects which use this as a module. The vendor.js, vendor.css, and main.css files will be quite large and often will repeat dependencies present in your main projects which includes this module e.g. bootstrap, angular, angular-bootstrap and font-awesome.

It is strongly suggested that you make the bower dependencies of this project dependencies of the parent project, and only include scripts/scripts.js and the sass/ folder. Include the scripts/scripts.js as part of your index.html and process the sass/ folder along with your own sass, note that it expects bower_components to be in the path.