update readme, history, version, for strict option

HISTORY.md

@@ -1,4 +1,5 @@
 ## Release History
+* 2015-02-27 v1.1.0 Enhancement: add `strict` option and change behavior to be `false` by default. Previous behavior was equivalent to `strict=true`.
 * 2015-02-26 v1.0.2 Fix: pass file missing errors up through callbacks
 * 2015-02-18 v1.0.1 use relativeTo with URLs to resolve web paths; use https: as default when paths start with //
 * 2015-01-01 v1.0.0 initial release: Forked and rewritten from grunt-inline with the goal of providing additional use cases and a new API

README.md

@@ -67,6 +67,9 @@ If cssmin is assigned `true`, CSS will be minified before inlined.
 #### `uglify`, Boolean, default `false`
 If uglify is assigned `true`, JavaScript file will be minified before inlined.
 
+#### `strict`, Boolean, default `false`
+When strict is `true`, a missing resource will cause the inliner to halt and return an error in the callback. The default behavior is to log a warning to the console and continue inlining with the available resources, which is more similar to how a web page behaves.
+
 
 ## Contributing
 In lieu of a formal styleguide, take care to maintain the existing coding style. Add unit tests for any new or changed functionality. Run tests with `npm test`.

package.json

@@ -6,7 +6,7 @@
   },
   "name": "web-resource-inliner",
   "description": "Inlines img, script and link tags into the same file.",
-  "version": "1.0.2",
+  "version": "1.1.0",
   "keywords": [
     "inline",
     "js",