Update dotenv to the latest version π
Version 5.0.0 of dotenv was just published.
| Dependency | dotenv |
|---|---|
| Current Version | 4.0.0 |
| Type | devDependency |
The version 5.0.0 is not covered by your current version range.
If you donβt accept this pull request, your project will work just like it did before. However, you might be missing out on a bunch of new features, fixes and/or performance improvements from the dependency update.
It might be worth looking into these changes and trying to get this project onto the latest version of dotenv.
If you have a solid test suite and good coverage, a passing build is a strong indicator that you can take advantage of these changes directly by merging the proposed change into your project. If the build fails or you donβt have such unconditional trust in your tests, this branch is a great starting point for you to work on the update.
Commits
The new version differs by 11 commits.
472db2e5.0.095aa929use explicit full path to form more informative error messages (#237)6b07aceMerge pull request #255 from SpainTrain/patch-1e767940README: link to dotenv-webpack project62a2afbLinking to run.env in README (#246)46ec97dMerge pull request #235 from RodrigoEspinosa/patch-1ce68a75Add link to lookenv in README40e9efcShaved a few bytes off by removing a ternary. (#222)bf06a9cImprove documentation (#207)25bf5addo not override set vars with falsy values (#203)825c1b2Syntax highlighting for .env content in README (#167)
See the full diff
FAQ and help
There is a collection of frequently asked questions. If those donβt help, you can always ask the humans behind Greenkeeper.
Your Greenkeeper bot :palm_tree:
Version 5.0.1 just got published.
Version 6.0.0 just got published.
- The
devDependencydotenv was updated from4.0.0to6.1.0.
- The
devDependencydotenv was updated from4.0.0to6.2.0.