To automate maintenance of dependency versions in `express-cli.js`

[oscard0m]

Right now the generation of the package.json to scaffold with its corresponding dependencies has hard-coded values of the names of the packages to use and its corresponding version.

This implies a manual maintenance of the version of the packages whenever there is a new release. This can be specially critical to not scaffold to users packages with vulnerabilities (which are already fixed in greater versions).

---

I would like to discuss a solution for this and also, I would be open to participate with my first contribution on this repository if possible :)

[oscard0m]

I was doing a follow up on my created issues and I come up with this one which has been inactive for a few days already. After checking commit history and top committers to the repo, I come with you @dougwilson. In case I'm addressing to the right maintainer Douglas:

1. Is this repo maintained?
2. Would you like to get help on maintaining it?

[dougwilson]

Well, I'm not sure how I didn't get an email or something for your first issue. Yes, if there is some kind of way to automate it, that would be awesome. I would guess something along the lines of check if there are new versions, bump one, run the test suite to make sure ithe update didn't need some change in the scaffolding and then commit or something?

[oscard0m]

Well, I'm not sure how I didn't get an email or something for your first issue. Yes, if there is some kind of way to automate it, that would be awesome. I would guess something along the lines of check if there are new versions, bump one, run the test suite to make sure ithe update didn't need some change in the scaffolding and then commit or something?

@dougwilson Opened PR. You can read the details in the PR.