Skip to content

Commit

Permalink
node packaged manuscript
Browse files Browse the repository at this point in the history
  • Loading branch information
James Halliday committed Jun 2, 2014
1 parent 9d676e9 commit c0defec
Show file tree
Hide file tree
Showing 3 changed files with 26 additions and 1 deletion.
6 changes: 6 additions & 0 deletions bin/cmd.js
Original file line number Diff line number Diff line change
@@ -0,0 +1,6 @@
#!/usr/bin/env node

var fs = require('fs');
var pager = require('default-pager');

fs.createReadStream(__dirname + '/../readme.markdown').pipe(pager());
8 changes: 7 additions & 1 deletion package.json
Original file line number Diff line number Diff line change
Expand Up @@ -18,5 +18,11 @@
"email": "mail@substack.net",
"url": "http://substack.net"
},
"license": "cc-by-3.0"
"license": "cc-by-3.0",
"dependencies": {
"default-pager": "^1.0.1"
},
"bin": {
"browserify-handbook": "bin/cmd.js"
}
}
13 changes: 13 additions & 0 deletions readme.markdown
Original file line number Diff line number Diff line change
Expand Up @@ -27,6 +27,7 @@ front or backend alike.

- [introduction](#introduction)
- [table of contents](#table-of-contents)
- [node packaged manuscript](#node-packaged-manuscript)
- [node packaged modules](#node-packaged-modules)
- [require](#require)
- [exports](#exports)
Expand Down Expand Up @@ -75,6 +76,18 @@ front or backend alike.
- [browser-unpack](#browser-unpack)
- [plugins](#plugins)

# node packaged manuscript

You can install this handbook with npm, appropriately enough. Just do:

```
npm install -g browserify-handbook
```

Now you will have a `browserify-handbook` command that will open this readme
file in your `$PAGER`. Otherwise, you many continue reading this document as you
are presently doing.

# node packaged modules

Before we can dive too deeply into how to use browserify and how it works, it is
Expand Down

0 comments on commit c0defec

Please sign in to comment.