Tin NPM | npm.io

tin

Easily manage NPM, component, and bower package files.

Why?

Managing Node.js and browser side JavaScript packages can be a pain in the ass. Editing multiple fields in package.json (Node.js/NPM), component.json (browser/component), and bower.json (browser/bower) is tedious. Tin makes this easier.

Installation

npm install -g tin

Specs

component: https://github.com/component/component/wiki/Spec
npm: https://npmjs.org/doc/json.html
bower: https://docs.google.com/document/d/1APq7oA9tNao1UYWyOm8dKqlRP2blVkROYLZ2fLIjtWc/edit (not sure if this is the most to date one)

Usage

Any of the three files package.json, component.json, and bower.json must exist. Tin will not create these files if they don't exist and they're not proper JSON.

Usage: tin [options]

Options:

-h, --help                                    output usage information
-p, --path [path]                             The path that contains the package files. Defaults to the current directory.
--create                                      If any of the files don't exist, it creates them.
--check                                       Check to verify files are valid. Don't use in conjunction with any other options.
-d, --desc [description]                      Update package descriptions.
-k, --keywords [keywords]                     Add to package keywords.
-m, --main [script]                           Update main script file.
-n, --name [name]                             Update name of the package.
-r, --repo [repo]                             Update source repository (GitHub shorthand).
-v, --version [version]                       Update package versions.
-b, --bump [major, minor, patch, prerelease]  Bump package version by increment