Maybe not "ideal", but useful as a troubleshooting step nonetheless. And if it's from "global" tools that yarn installed, clean those up too. And if it does then that raises other concerns, beyond the scope of Valet.īut, one way to rule it out is to delete everything yarn installed, and then remove the node_modules dir, and reboot. I wouldn't have expected a simple yarn update to do anything that's interfering, unless it's gone and installed some package that set some new ENV vars that CURL uses, or something that provides DNS services and now is clashing with dnsmasq or osx core. You could also install an alternate Client to override the default of using CURL: You could maybe enable Guzzle's debug mode, to get more information back:
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |