anyone ever see that type of error after an npm update? :-\