I recently spent an embarrassing amount of time chasing a “green” Azure Static Web Apps (SWA) deployment that still left me with a dead API—and even GitHub Copilot kept looping on red herrings, unable to spot what was really wrong. The culprit was a private workspace package - @acme/shared-core - that the Functions runtime could not see once Oryx built the managed API. This post walks through what happened, why the failure was completely silent from SWA’s point of view, and how I now bundle local packages (including their transitive npm dependencies) before handing anything to Oryx.
