organization · inferred from evidence
Braze
The organization behind the @braze/web-sdk, which acknowledged the circular dependency issue.
- Waiting for the Braze SDK to be ready when loaded via GTM
When the Braze Web SDK loads async (e.g. via GTM), don't poll window.braze yourself.
- Braze web SDK unusable without 'unsafe-eval' Content Security Policy
Teaches the verified fix from a real braze support thread: braze web SDK unusable without 'unsafe-eval' Content Security Policy
- Circular dependency warnings from @braze/web-sdk with Vite / Rollup
Exclude the SDK from Vite's dev-server dependency optimization so it is loaded as-is instead of being pre-bundled: add `@braze/web-sdk` to `optimizeDeps.exclude` in vite.config (e.g. `optimizeDeps: { exclude: ['@braze/web-sdk'] }`).
- subscribeToContentCardsUpdates not firing in Next.js (Braze web SDK)
What this covers: On Next.js with Braze Web SDK 4.1.0 installed via npm, `subscribeToContentCardsUpdates((cards) => ...)` never fires after `initialize()` succeeds. The fix that worked: Content Cards are not pushed instantly at session star