when xcode fails to load swift package dependency, it just fail silently, it removes targets from my build menu quietly and say nothing about why that fail, leaving me stranded and confused and spent hours to figure out why the target defined in the package.swift file just doesn't show up. I remember "UX" used to be the buzz word Steve Jobs bragging about?

why can't apple even provide a consistent interface to load swift package? "add package dependency" interface allows you to add remote package, but doesn't allow you add local in development swift package. to do that, you will have to "drag and drop"... why can't apple just add a button on the same interface for navigate local package? is this suppose to be some hidden up up down down left right left right konami secret thing?

Added vapor core swift package to my project so that I can use some of the extensions, had to `rm -rf ~/Library/Developer/Xcode/DerivedData/` to make xcode realise the repo is actually exist.
Then I set the Core package as dependency of one of the targets, XCode complaints "unknown package Core", ok fine then I remove Core dependency, Core complaints "dependency Core is not used by any target".
How can xcode comes to this contradicting conclusion is out of my imagination, it just never gonna be happy about however i write.