raymondcamden’s Twitter Archive—№ 59,506

And serves me right - not a hyper issue. Hyper just had a newer instance of the shell. It's really an issue w/ a npm problem.