Skip to content

Documentation / @warp-drive/build-config / index / WarpDriveConfig

ts
type WarpDriveConfig = object;

Defined in: index.ts:52

Properties

compatWith?

ts
optional compatWith: `${number}.${number}`;

Defined in: index.ts:100

The most recent version of the library from which all deprecations have been resolved.

For instance if all deprecations released prior to or within 5.3 have been resolved, then setting this to 5.3 will remove all the support for the deprecated features for associated deprecations.

See deprecations for more details.


debug?

ts
optional debug: Partial<InternalWarpDriveConfig["debug"]>;

Defined in: index.ts:66

An object of key/value pairs of logging flags

see debugging for the available flags.

ts
{
 LOG_CACHE: true,
}

deprecations?

ts
optional deprecations: Partial<InternalWarpDriveConfig["deprecations"]>;

Defined in: index.ts:115

An object of key/value pairs of logging flags

see deprecations for the available flags.

ts
{
  DEPRECATE_THING: false,
}

features?

ts
optional features: Partial<InternalWarpDriveConfig["features"]>;

Defined in: index.ts:132

An object of key/value pairs of canary feature flags for use when testing new features gated behind a flag in a canary release version.

see features for the available flags.

ts
{
  FEATURE_A: true,
}

includeDataAdapterInProduction?

ts
optional includeDataAdapterInProduction: boolean;

Defined in: index.ts:87

By default, the integration required to support the ember-inspector browser extension is included in production builds only when using the ember-data package.

Otherwise the default is to exclude it. This setting allows to explicitly enable/disable it in production builds.


polyfillUUID?

ts
optional polyfillUUID: boolean;

Defined in: index.ts:75

If you are using the library in an environment that does not support window.crypto.randomUUID you can enable a polyfill for it.

Released under the MIT License.