Automation to verify NPM dependencies/scripts in project templates #308
Description
Is your feature request related to a problem? Please describe.
New project templates come with NPM dependencies and corresponding scripts in package.json. For example, we currently define the ESLint dependency in package.json as "eslint": "^7.24.0",. Over time and as other packages are added/upgraded, these dependencies may become out of date or incompatible with each other.
Describe the solution you'd like
It would be valuable to have automated tests that verify regularly that these dependencies are still valid and the corresponding NPM scripts in package.json work. A very simple "hello world" type project could be created using the project templates and then after installing the dependencies the lint, format, test, etc. commands could be run to verify they work for basic usage.
Describe alternatives you've considered
Alternative is to leave things how they are now and wait for customers or other internal developers to notice something is broken and file a bug report or PR.
Additional context
#299 was recently merged to fix these broken template dependencies. The original issue was filed almost 4 months prior here: #246.