node package manager
Share your code. npm Orgs help your team discover, share, and reuse code. Create a free org ยป


________________  ___________/_/____________
_  ___/  __ \  / / /_  ___/_  /_  _ \_  ___/
/ /__ / /_/ / /_/ /_  /   _  / /  __/  /    
\___/ \____/\____/ /_/    /_/  \___//_/ -> package.json (dynamic npm packages in CoffeeScript)


Compiling a file to a package.json isn't as simple as it seems.

Since CoffeeScript wraps objects in order to make them assignable statements. courier will love and hold you through the night. Oh and it will cleanup the generated JavaScript to keep npm happy ^w^


npm -g install courier

Why a global install?

Just because.


Using courier couldn't be simpler.

  1. Write your npm package ("package.json") in CoffeeScript and save as
  2. Run courier against your project.

You will now see package.json alongside in the root of your project; ready to be installed or linked with npm.


Use the -p (--print) flag for a noisy delivery.


Since courier utilises dynamic CoffeeScript and not static JSON, npm packages can be made dynamic.

For instance, the following

name: 'node-foo'

description: 'extends node with foo'

date: new Date

...would produce the following package.json...

  "name": "node-foo",
  "description": "extends node with foo",
  "date": "2011-02-23T09:25:14.491Z"

For a concrete example of this behaviour, look no further than the of this very project; where the VERSION file is read to dynamically version the npm package.