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

jumpstart-black-coffee

v0.7.0

Published

Jumpstart template for a nice CoffeeScript npm module

Downloads

49

Readme

jumpstart-black-coffee

Jumpstart template for an open source JavaScript module that's written in CoffeeScript.

This template assumes:

  • you're using GitHub;
  • you want the GitHub repository name to be the same as the npm module name;
  • you want to use Mocha for writing tests, or you don't mind having it available;
  • you want to release your code under the MIT License.

There are configuration files for Textmate 2 and Travis CI.

The generated README.md file includes status badges for Travis CI and David DM.

Installation

npm install jumpstart
npm install jumpstart-black-coffee

Configuration

Jumpstart looks for a .jumpstart.json file inside your current working directory - or if not found, in your home directory - for global values for the various placeholders. See Jumpstart documentation for

Usage

Starting a new project

jumpstart dirname black-coffee

You will be asked to provide values for the placeholders inside the black-coffee template. Jumpstart then creates a new directory dirname containing the filled-out template.

Notes on proper placeholders values:

  • github-ownername -- will be used for the github repository url. Set it either to the same as github-username, or to the name of a github organization you are a member of.
  • module-is-private -- either the string true or the string false. Jumpstart does not know about booleans. If you give it any other value (e.g. leave it blank), you'll end up with invalid json in the generated files.

After creating a new project it's recommended you run the following command once:

Initializing the new project

Go to your newly created project directory.

npm run jumpstart

This command

  • runs npm install, which will install the dev-dependencies (coffee-script, mocha and pre-commit)
  • creates an empty .coffee file named after the module in both src/ and test/.

Running npm run jumpstart afterwards is optional.

Conveniences during development

During development, you can make use of the following commands.

  • npm run build -- compiles all .coffee files in src/ and outputs into lib/.
  • npm run watch -- let coffee watch src/ for changes, and compile any changed .coffee file to lib/.
  • npm test -- runs npm run build, and mocha tests afterwards

These commands require the dev-dependencies to be installed. You can do so with npm install.

When you do npm publish, npm test will be run first, ensuring that the JavaScript code you're publishing is both fresh and working (in so far it's covered by tests). When you attempt to make a commit with git, npm test will also be run first.

See also the Jumpstart documentation.

License

jumpstart-black-coffee is released under the MIT License. Copyright (c) 2016 Braveg1rl