chore(npm): adds package-lock.json files

[timbru31]

Ref apache/cordova#4

Platforms affected

Motivation and Context

Description

Testing

Checklist

• I've run the tests to see all new and existing tests pass
• I added automated test coverage as appropriate for this change
• Commit is prefixed with (platform) if this change only applies to one platform (e.g. (android))
• If this Pull Request resolves an issue, I linked to the issue in the text above (and used the correct keyword to close issues using keywords)
• I've updated the documentation if necessary

[erisu]

@jcesarmobile @raphinesse What do you think about adding the package-lock.json to the template_src which is the base cordova project? cordova create projectName

[raphinesse]

I would neither add the top-level lockfile nor the one in template_src. The top-level file is useless as this package doesn't have any dependencies.

Regarding the template file: we potentially change the package name and version present in the template during cordova create. Those values will then differ between package.json and package-lock.json. npm would fix this on the next install, but at that point the file might already be committed into version control. Moreover I don't see a real benefit here.

So I think adding this would be more trouble than it's worth 👎

[timbru31]

Convinced! :)