upgrade dependencies (#338)

.npmignore

@@ -1,8 +1,8 @@
-coverage/
 .nyc_output/
-test/
+tests/
 .editorconfig
 .npmignore
 .travis.yml
+appveyor.yml
 CONTRIBUTING.md
 dotenv.png

CONTRIBUTING.md

@@ -1,16 +1,16 @@
 # Contributing
 
-1. Fork it
-2. `npm install`
+1. [Fork it](https://help.github.com/articles/fork-a-repo/)
+2. Install dependencies (`npm install`)
 3. Create your feature branch (`git checkout -b my-new-feature`)
 4. Commit your changes (`git commit -am 'Added some feature'`)
-5. `npm test`
+5. Test your changes (`npm test`)
 6. Push to the branch (`git push origin my-new-feature`)
-7. Create new Pull Request
+7. [Create new Pull Request](https://help.github.com/articles/creating-a-pull-request/)
 
 ## Testing
 
-We use [lab](https://github.com/hapijs/lab) and [should](https://github.com/shouldjs/should.js) to write BDD test. Run our test suite with this command:
+We use [TAP](https://github.com/tapjs/node-tap) to write tests. Run our test suite with this command:
 
 ```
 npm test

README.md

@@ -71,7 +71,7 @@ _Alias: `load`_
 
 `config` will read your .env file, parse the contents, assign it to
 [`process.env`](https://nodejs.org/docs/latest/api/process.html#process_process_env),
-and return an Object with a `parsed` key containing the loaded content or an `error` key if it failed.  
+and return an Object with a `parsed` key containing the loaded content or an `error` key if it failed.
 
 ```js
 const result = dotenv.config()
@@ -95,7 +95,7 @@ You can specify a custom path if your file containing environment variables is
 named or located differently.
 
 ```js
-require('dotenv').config({path: '/full/custom/path/to/your/env/vars'})
+require('dotenv').config({ path: '/full/custom/path/to/your/env/vars' })
 ```
 
 #### Encoding
@@ -106,7 +106,7 @@ You may specify the encoding of your file containing environment variables
 using this option.
 
 ```js
-require('dotenv').config({encoding: 'base64'})
+require('dotenv').config({ encoding: 'base64' })
 ```
 
 ## Parse