Require NPM 18

[mvidner]

Problem

We spent some hours debugging a problem where the web frontend was not updated because the machine had NPM 17 which is no longer enough

Solution

Tell zypper, and npm, to install v 18 at least

Testing

• Tested manually: ran ./setup.sh with

-  "engines": { "node": ">=18" },
+  "engines": { "node": ">=1899" },

npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE   package: undefined,
npm WARN EBADENGINE   required: { node: '>=1899' },
npm WARN EBADENGINE   current: { node: 'v19.1.0', npm: '8.19.3' }
npm WARN EBADENGINE }

[mvidner]

@dgdavid says "it was a consequence of #331 I believe"

OK, anyway I hope package.json has a way to say "complain loud and clear unless npm >= 18"

[coveralls]

Coverage remained the same at 76.106% when pulling 9450ff3 on require-node18 into 09d561d on master.

[mvidner]

Ha!!
https://docs.npmjs.com/cli/v6/configuring-npm/package-json#engines

You can specify the version of node that your stuff works on:

{ "engines" : { "node" : ">=0.10.3 <0.12" } }

And, like with dependencies, if you don't specify the version (or if you specify "*" as the version), then any version of node will do.

[mvidner]

$ rpm -q --provides npm19
...
nodejs-npm = 19.1.0
npm = 19.1.0   # match here
npm(npm) = 8.19.3
npm19 = 19.1.0-1.1
npm19(x86-64) = 19.1.0-1.1