Document using locally

Fixes #2 🎉

Author: hughsk

README.md

@@ -12,7 +12,7 @@ Install the loader using [npm](https://npmjs.com/):
 npm install --save ify-loader
 ```
 
-You can then update your `webpack.config.js` in a similar fashion to the following to add browserify transform support to your project:
+You can then update your `webpack.config.js` in a similar fashion to the following to add browserify transform support to your project's dependencies:
 
 ``` javascript
 module.exports = {
@@ -29,6 +29,42 @@ module.exports = {
 }
 ```
 
+### Using transforms in your project
+
+Note that you're also free to apply this loader to files in your own project. Include the following in your project's `webpack.config.js`:
+
+``` javascript
+module.exports = {
+  module: {
+    postLoaders: [
+      // support local package.json browserify config
+      {
+        test: /\.js$/,
+        loader: 'ify'
+      }
+    ]
+  }
+}
+```
+
+Any browserify transforms you include in `package.json` will get picked up and applied this way:
+
+``` json
+{
+  "name": "my-project",
+  "dependencies": {
+    "glslify": "5.0.0",
+    "brfs": "1.4.2"
+  },
+  "browserify": {
+    "transform": [
+      "glslify",
+      "brfs"
+    ]
+  }
+}
+```
+
 ## Why?
 
 When given the choice, I lean more in favour of [browserify](http://browserify.org) for its simplicity and compatability with node.js — however from time to time I need to work on projects that use webpack. The thing I run into issues with most often when switching between the two is the difference in how webpack handles source transforms compared to browserify.