ES7 Migration - Fixing package versions

cybertk / abao

REST API automated testing tool based on RAML

MIT License

354 stars 59 forks source link

ES7 Migration - Fixing package versions #228

Open oshalygin opened 7 years ago

oshalygin commented 7 years ago

We ought to fix the dependency versions so that future fresh builds do not pull unwanted breaking change package updates. The node community is pretty inconsistent in maintaining SEMVER(which we should follow), and as such, relying on wildcards such as ^ and ~ will bite us in the long run.

cybertk commented 7 years ago

+1 for explicitly versioning(^), and let GreenKeeper handles the updating, GreenKeeper already provisioned.