Merged for inclusion in 3.10. Thanks, Galen, Tiffany, Bill, Andrea, Ruth, and all testers and AIG participants!
I also added two follow-up commits
* Since this development migrates eg2's package-lock.json to lockfileVersion 2, I've taken the liberty of bumping the node version and migrating the other package-lock.json files. Without this change, whenever I run `npm i`, I get the message: "This version of npm is compatible with lockfileVersion@1, but package-lock.json was generated for lockfileVersion@2. I'll try to do my best with it!" and the lockfile gets migrated back to lockfileVersion 1.
* Fixed a few issues identified by the new linter
Merged for inclusion in 3.10. Thanks, Galen, Tiffany, Bill, Andrea, Ruth, and all testers and AIG participants!
I also added two follow-up commits
* Since this development migrates eg2's package-lock.json to lockfileVersion 2, I've taken the liberty of bumping the node version and migrating the other package-lock.json files. Without this change, whenever I run `npm i`, I get the message: "This version of npm is compatible with lockfileVersion@1, but package-lock.json was generated for lockfileVersion@2. I'll try to do my best with it!" and the lockfile gets migrated back to lockfileVersion 1.
* Fixed a few issues identified by the new linter