Those pesky async functions just doing whatever they want when they want.... now waiting for results to update info
As mentioned re: fixing git history-- I had to remove and re-clone the repo. This meant I needed to run npm install again, which resulted in the package-lock changes...? It runs for me! don't understand build systems/setups well enough to know why it updated tho... hopefully fine?
Fix for #41
Those pesky
asyncfunctions just doing whatever they want when they want.... now waiting for results to update infoAs mentioned re: fixing git history-- I had to remove and re-clone the repo. This meant I needed to run
npm installagain, which resulted in the package-lock changes...? It runs for me! don't understand build systems/setups well enough to know why it updated tho... hopefully fine?