Merge branch 'master' into programs-folder

CHANGELOG.md

@@ -1,13 +1,17 @@
 Change History
 ==============
 
+v1.0.7
+----
+* Enable meteorFolder to be absolute. Thanks to [@jedwards1211](https://github.com/jedwards1211) for his [PR](https://github.com/luisherranz/meteor-imports-webpack-plugin/pull/6).
+
 v1.0.6
 ----
 * Fix for undefined __meteor_runtime_config__.
 
 v1.0.5
 ----
-* @adam187 fix for HMR.
+* [@adam187](https://github.com/adam187) fix for HMR.
 
 v1.0.4
 ----

README.md

@@ -76,7 +76,7 @@ All the `config` object is passed to `__meteor_runtime_config__` variable so if
 
 #### config.meteorFolder
 
-The subfolder where your Meteor project is located.
+The subfolder where your Meteor project is located. It can be an absolute path as well.
 
 ```javascript
 new MeteorImportsPlugin({
@@ -257,6 +257,10 @@ Webpack is a powerful but complex tool, with a non-friendly API, so reading code
 - [ES2015 imports in Wepack with Meteor 1.3 server](https://github.com/luisherranz/meteor-imports-webpack-plugin-examples/tree/master/es2015-meteor1.3)
 - [ES2015 imports in Wepack with React, HMR and Meteor 1.3 server](https://github.com/luisherranz/meteor-imports-webpack-plugin-examples/tree/master/es2015-meteor1.3-react)
 
+## App Skeletons
+
+- **[Crater](https://github.com/jedwards1211/crater) from [@jedwards1211](https://github.com/jedwards1211)**: Meteor(/React) app skeleton that runs your userland code with pure Webpack/Babel instead of isobuild.
+
 ## The bad things
 
 - **Dev servers**: if you add or remove Meteor packages, you have to restart your dev servers, both Webpack and Meteor.

package.json

@@ -1,6 +1,6 @@
 {
   "name": "meteor-imports-webpack-plugin",
-  "version": "1.0.6",
+  "version": "1.0.7",
   "description": "Webpack plugin to import and use Meteor packages like if they were real NPM packages.",
   "main": "index.js",
   "scripts": {},