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-spa-project

v0.0.1

Published

Yeoman generator for creating a single-page application with unit and e2e testing integrated and utilizing best practices for react, flux, and other front-end frameworks.

Downloads

14

Readme

generator-spa-stack Build Status

Yeoman generator for creating a single-page application with unit and e2e testing integrated and utilizing best practices for react, flux, and other front-end frameworks.

Technology Stack

Unit Testing

End-to-End Testing

Build Automation

UI

Routing

Miscellaneous

Generated Project

Project Structure

.
|-- src
|    |-- app
|        |-- actions
|        |-- components
|        |-- dispatcher
|        |-- lib
|        |-- stores
|    |-- images
|    |-- styles
|        |-- partials
|        +-- app.styl
|    +-- index.html
|-- test
|   |-- unit
|        |-- lib
|            +-- {{unit being tested}}-spec.js
|   |-- e2e
+-- .bowerrc
+-- .jshintrc
+-- bower.json
+-- gulpfile.js
+-- package.json

Build Output Structure

.
|-- public
|    |-- images
|    |-- js
|        +-- index.js
|    |-- styles
|        +-- index.css
|    |-- vendor
|        |-- {{bower third party dependency}}
             +-- {{bower main files}}
|    +-- index.html

Usage: gulp Tasks

To run the site, use the following command

gulp dev

To run all tests, use the following command

gulp tests

To run only unit tests, use the following command

gulp tests-unit

To run only end-to-end tests, use the following command

gulp tests-e2e

To create a development build, use the following command

gulp build

Build Customization

Any of the above accepts an optional CLI parameter to configure to build. An example is generated and named example.env.build.config.js and is located in the root of the project. Passing the optional parameter would look like this:

gulp build --buildConfigFile './example.env.build.config.js'

Production Builds

For production builds, the build.config.js can be updated to appropriate values to utilize CDNs over local resources.

  • third-party dependencies use their respective CDN as specified by the build's configuration file
  • application specific assets (css, javascript, images) utilize a CDN as specified by the build's configuration file