fabric-app-bootstraplisted

# Fabric App Bootstrap Stand up and deploy a Microsoft Fabric App (preview) from the CLI, including fully headless with a service principal. Distilled from a real production-shaped build; every gotcha here cost real hours. ## What a Fabric App is (and is not) One workspace item ("App", backed by an AppBackend) with three managed children: | Service | What it gives you | |---|---| | **Static hosting** | your built SPA on a public URL (served from OneLake) | | **SQL Database** | schema generated from TypeScript `@entity()` decorators | | **GraphQL API** | data plane the client SDK talks to, behind Entra SSO | **It will NOT host:** Node SSR (no Next.js server), server-held secrets (no BFF with a client secret), Python or any custom runtime. The deploy is a zip of `dist/`, capped at **100 MB compressed**. End-user auth on a deployed app is **Entra SSO only**. **Porting check:** if the existing app fetches server-side with a secret, that code cannot board. Visual/client code survives intact. Route the data layer through one of the companion skills. **Porting from Next.js (proven pattern, ~30 min/page):** rebuild the shell as a Vite SPA, then alias `next/link` and `next/navigation` to two ~25-line shims in `vite.config.ts` (`resolve.alias`) so page components, CSS modules and shared components copy over VERBATIM with zero import rewrites. Wrap async server components in a client component with `useState` + `useEffect`. Re-export the old data layer's types and swap only the i