Database scripts and Google Cloud Functions were tangled due to legacy development reasons, and it was time to separate them as they represent two completely different concerns. They shared one package.json file (with one scripts section) and one node_modules dependency folder.
In this PR, I extracted db_scripts to a top-level directory, and uninstalled dependencies in both package.jsons as appropriate.
I've confirmed the database script index.ts to run correctly when built, and that Cloud Functions can be served locally.
(PS, I omitted the built folder from the jest config in db_scripts, running npm test there tested against the built code as well).
Summary
Database scripts and Google Cloud Functions were tangled due to legacy development reasons, and it was time to separate them as they represent two completely different concerns. They shared one
package.jsonfile (with onescriptssection) and onenode_modulesdependency folder.In this PR, I extracted
db_scriptsto a top-level directory, and uninstalled dependencies in bothpackage.jsons as appropriate.I've confirmed the database script
index.tsto run correctly when built, and that Cloud Functions can be served locally.(PS, I omitted the built folder from the jest config in
db_scripts, runningnpm testthere tested against the built code as well).