The situation:
Using `@braze/web-sdk` 4.1.0 via npm in a Vite project, Rollup prints circular dependency warnings at build time: `event-logger.js -> braze-instance.js -> network-manager.js -> event-logger.js` and similar chains. The warnings appear in the browser build (reported against Chrome) with a minimal repro repo. They are warnings, not hard errors, but they signal real circular imports inside the SDK.
What actually fixes it (verified in the thread):
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 only affects the Vite dev server's pre-bundling; production Rollup builds still include the SDK normally, so there are no runtime errors. The reporter confirmed this workaround silences the warnings. Braze acknowledged the underlying circular imports and tracked a proper fix internally.