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

shshifter

v0.5.6

Published

New YUI build tool based on Gearjs, so let's shift some gears

Downloads

13

Readme

Shifter - Blazingly Fast YUI Builder

The purpose of this project is to replace YUI's use of our old ant Builder.

We have out grown our old builder, so it was time to build a new one!

Linting

As of 0.1.0, JSHint is the default lint tool used by shifter. We maintain a list of our lint preferences in the yui-lint project. shifter will default to our rules unless --lint config is passed. Then it will search up the file tree and attempt to load your custom .jshintrc file.

Documentation

Documentation can be found here

Build Status

Build Status

Install

npm -g install shifter

Some Options

More detail can be found in the documentation

$ shifter -h

blazingly fast builds with shifter

pass no arguments and shifter will build the module from the current directory

   -v/--version            show version
   -h/--help               show this stuff
   -m/--modules <module>   limit the modules to build (array: -m foo -m bar)
   --strict                add "use strict" to module wrapper
   --walk                  Walk the current directory and shift all builds. (cd yui3/src && shifter --walk)
                               -m/--modules also supported here for filtering
   --watch                 Watch the current module and rebuild on file change (if meta file, a loader build will launch)
                               --quiet to mute stdout from sub build

Usage

Shifter will parse your current *.properties files and convert them into a build.json file that it can process. It only imports the relevant settings required to build the module.

It does not import module meta-data

Instead, Shifter parses the meta-data from the modules meta/*.json files and uses that instead. So you don't have to declare your meta-data in more than one place now.

Watching

Shifter can watch your module for changes and build for you. It will only watch files in the ./js, ./css, ./assets and ./meta directories. If a file is changed, it will rebuild the current module. If a meta file is changes, Loader will also be built (requires latest code).

Migrating

Shifter is designed to work side by side with our current builder (for now) so you don't have to switch over to using it fully if it doesn't work properly for you. Just don't delete your *.properties files until you are sure that Shifter builds your module properly. If it doesn't, file a ticket and we'll get it fixed up ASAP.

Shifter will read a build.json file if it exists, if one doesn't and it finds a *.properties file it will generate the build.json from them. So if you have issues with the build, just delete the build.json file and have Shifter regenerate it after your issue is fixed.

GearJS

Shifter is built using GearJS