Closed aaronjudd closed 8 years ago
I haven't seen this issue since it happened on that one day this was reported, so I'm going to assume it's all set for now.
I was getting this on my last update of the CLI. I googled it this am, and found that there were some specific node versions that had this issue recently. I updated to latest node and haven't seen since. Also, was sometimes seeing this on other package installs, so I'd agree it's resolved.
Ok, cool. Thanks for the info.
On every upgrade I see warnings, but everything seems to still work fine.
reaction
runs fine, without warnings. Only reporting here, as it does happen on every upgrade and while I suspect it's outside the reaction-cli environment, it's worth tracking for a bit and investigating.