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

fairmont-build-tools

v1.0.2

Published

Shared tooling for building fairmont packages

Downloads

16

Readme

Build Tools

Shared tooling for building Fairmont packages, among others.

Usage

tools = require "fairmont-build-tools"
{target} = tools require "gulp"

target "npm"

This will get you the tasks associated with the npm target preset. This includes:

  • npm:build — Compiles CoffeeScript in lib to build/npm/lib and CoffeeScript tests in test to build/npm/test.

  • npm:test — Runs the compiled tests.

  • npm publish — Publishes to NPM.

Presets

The only meaningful preset at this time npm. Presets esm and www are reserved. Don't use these as tasks prefixes.

Built-In Tasks

The tasks build, test, and publish are all defined to iterate on active targets (any targets for which tasks have been defined) and execute the corresponding tasks, ex: npm:build.

In addition, these tasks are also defined:

  • git:tag — Tag the current release using the version in the package.json file and push the tags to master. Runs automatically on npm:publish.

  • clean — Deletes the entire build directory. Since each target defines it's own clean task (which should delete the target directory), you shouldn't need this.

Configuring package.json

Remember, the files you're publishing will be in build/npm. The files, directories, and main properties should reflect this. Define test to be gulp test.

Watching Files

Coming soon.