breaking: drop node engine requirement

[erisu]

Motivation, Context & Description

• In a production environment, our plugins do not execute node related code and does not need the engine check.
• In the environment of developing this plugin, the linting tool is the only node based library which has already defined the node engine requirement. We do not need to set the engine since the lint tool will report, when not valid.

Example:

npm WARN notsup Unsupported engine for @cordova/eslint-config@3.0.0: wanted: {"node":">= 10.13.0"} (current: {"node":"8.17.0","npm":"6.13.4"})
npm WARN notsup Not compatible with your version of node/npm: @cordova/eslint-config@3.0.0

[jcesarmobile]

Can’t we just remove the node entry? Other plugins don’t have it (didn’t check all, but didn’t see in 3 random ones)

[erisu]

Yeah, we could probably remove the node engine from our plugins.

The only thing that has a node requirement is the linting tool, but it is only for development purposes.

Our plugins do not use any hook-scripts or node-specific code in production, so there is no node execution. Only the Cordova CLI tooling, which does the copying and merging of the src or www content, has the requirement.

I think it is safe to drop it.

[jcesarmobile]

Yeah, I can check them all later, but so far I’ve checked 3 and they didn’t have it

[jcesarmobile]

I have reviewed all the plugins (even archived and deprecated ones) and none had a node requirement, so we are good