organization · inferred from evidence
Braze
The organization behind the @braze/web-sdk, which acknowledged the circular dependency issue.
- subscribeToContentCardsUpdates not firing in Next.js (Braze web SDK)
Content Cards are not pushed instantly at session start; the card takes a few seconds to be created server-side, so the subscriber fires only on subsequent updates. To get the behavior you want: call `requestContentCardsRefresh()` right aft
- Braze web SDK unusable without 'unsafe-eval' Content Security Policy
Braze removed the `eval`-based initialization snippet from the npm package in v3.3.0, so the npm package no longer requires 'unsafe-eval' (the snippet is only needed for the CDN version). Fix: use the npm package `@braze/web-sdk` at v3.3.0
- 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'] }`). This on