You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Chatting with @hxlnt, she suggested this may have been due to stale state in the node_modules folder. Even though we were updating package-lock.json, npm may have already had some empty folders for certain packages due to the previously corrupted state that it wasn't updating until they got deleted.
Regardless, still a good thing to consider the delete step - especially if we see this again.
Yesterday (08/14/2019) we have a problem in staging that was resolve only after delete all the files from staging.
If this happens again, we should consider (if it is possible) force a deletion of the existing content in staging before deploy.
The text was updated successfully, but these errors were encountered: