Downgrade package-lock.json back to v1

[pierlon]

Summary

As @westonruter pointed out, the .nvmrc points to the lts version of node, which would install node v14 and npm v6 by default. However, the package-lock.json is using the v2 syntax which is generated by npm v7 (and later). Attempting to run npm install with npm v6 causes the package-lock.json to produce a massive diff as it downgrades the lockfile back to v1.

Also to note, Gutenberg and WP Core also currently use npm v6 and have their package-lock.json files in v1 format. Downgrading our lockfile to v1 to align with theirs will allow us developers to work across these projects without much hassle.

Checklist

• My code is tested and passes existing tests.
• My code follows the Engineering Guidelines (updates are often made to the guidelines, check it out periodically).

[pierlon]

One thing to note also is when node v16 and npm v7 become LTS next month, we might have to update .npmrc to v14, if Gutenberg (or Core) is still using the lockfile v1 format.

[github-actions]

Plugin builds for d0c2a01 are ready 🛎️!

• Download development build
• Download production build

[pierlon]

Also to mention, Gutenberg is planning to upgrade their package-lock.json to v2 format: WordPress/gutenberg#33892. Once that is done Core should be on their way to update theirs as well: WordPress/wordpress-develop#1146 (comment).

[westonruter]

Thank you!