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

buildfirst-ci-by-example

v0.1.0

Published

_This repository is part of the **JavaScript Application Design: A Build First Approach** book's code samples_, the full original for the code samples [can be found here](https://github.com/bevacqua/buildfirst). You can [learn more about the book itself here](http://bevacqua.io/buildfirst "JavaScript Application Design: A Build First Approach").

Downloads

2

Readme

Continuous Integration Build Status

This repository is part of the Designing Javascript Applications: A Build First Approach book's code samples, the full original for the code samples can be found here. You can learn more about the book itself here.

This tutorial is part of the code samples accompanying the book in Chapter 4, about the release flow, deployments, and hosted application monitoring.

Introduction

Setting up CI is almost trivial in this day and age. In this repository we'll learn how to get ourselves up and running with Travis-CI. The first thing we'll need to do, is create a .travis.yml file at the project root. In this example, the file looks like:

language: node_js

node_js:
  - "0.10"

before_install:
  - npm install -g grunt-cli

script:
  - grunt ci --verbose --stack

There is even a linter for .travis.yml files, which you can use on lint.travis-ci.org, to verify the integrity of this file. The format is pretty self-descriptive, and we've covered the basics on the book.

All there's left, then, is to set up a ci task for Grunt. The task just runs jshint for this example, which isn't very useful because it will run the same in our development environments. We should configure the ci task to run unit, and integration tests as we'll examine in future chapters.

Configuring It

You'll probably want to try this example out yourself. First thing you'll need is a git repository that's configured to run on Travis. That's easy, you could just fork this one by following a series of simple steps.

Just click on the damn link already!

  • Click on your username if need be.

fork.png

Awesome! Now all we need to do is visit travis-ci, and click on Sign in with GitHub. If you don't have an account yet, you'll be prompted to create one, do that. It's free. Once you've signed in, visit your profile page, and click on Sync Now, so Travis gets all your GitHub repository information he needs. You'll get a list of public repositories you own.

repos.png

Turn username/ci-by-example on, wait for it, and then click on the little settings icon. Then simply follow the install notes. If Travis didn't fill them in for you, you'll need to enter your credentials: the username and API token, which can be found here.

Once that's done, clicking on Test Hook should trigger a build. A Build Status badge could now be yours!

[![Build Status](https://travis-ci.org/{you}/{project}.png)](https://travis-ci.org/{you}/{project})

And voilá!

badge.png

For more information you can visit the guide provided by Travis-CI.