Environments

FRVR.init() takes an environment argument:

FRVR.init('dev');    // development
FRVR.init('beta');   // beta/staging
FRVR.init('prod');   // production (default)

What each mode changes

Mode	Console logging	Backends	Default ads	Safety
dev	Verbose, color‑coded warnings	Staging / mocked	Test providers auto‑wired	Looser
beta	Verbose	Staging	Real providers	Loose
prod	Muted (unless you set FRVR.logger = console)	Production	Real providers	Strict

A warning banner logs in your browser console whenever you run anything other than prod, so you don’t forget to flip it.

Picking backends explicitly

Some modules accept an explicit backend URL that overrides whatever env would pick:

FRVR.config.features = {
  apiUrl: 'https://staging.crucible.frvr.com',
};

FRVR.config.cloudStorage = {
  playerStorage: { env: 'staging' },
};

Forcing verbose logs in prod

Set a logger before init():

FRVR.logger = console;
FRVR.init('prod');

Useful for debugging a production build in the field. Remove before shipping.

Dev channel

During local development, the easiest setup is the frvr-channel-dev bundle — it stubs ads, IAP, and other platform‑specific bits so you can click through flows without a live provider:

<script src="https://cdn.frvr.com/sdk/frvr-sdk.min.js"></script>
<script src="https://cdn.frvr.com/sdk/frvr-channel-dev.min.js"></script>

Ship with a real channel bundle (frvr-channel-web, -facebook-instant, -ios, …) — never the dev one.