Ensure all contrib repositories have `engines` defined

[joshwiens]

We have more than a few repos that don't have the engines field designated in the package.json

• Update all contrib repos with the same supported engines as webpack/webpack

  "engines": {
    "node": ">=4.3.0 <5.0.0 || >=5.10"
  },

[sapegin]

Any reason to skip 5.0—5.9? I’ve sent a PR to webpack-defaults.

[joshwiens]

There is a reason for it based on issues with those versions & webpack. I don't know what they are exactly, only that they exist.

[sapegin]

OK, I’ll add a comment in webpack-defaults then ;-)

[sukrosono]

I would suggest a done-list on first post, so we can track remaining work and it's progress.

[joshwiens]

Engines ranges come with webpack-defaults. Which is trackable here https://github.com/orgs/webpack-contrib/projects/5

[sukrosono]

it lead me 404, it's restricted scope? Nvm if you already have the checklist :smile: .

[joshwiens]

Organization project so probably but none the less, there is tracking across every project under contrib

[michael-ciniawsky]

Resolved by/in webpack-defaults