@snap/camera-kit
Version:
Camera Kit Web
118 lines (75 loc) • 4.08 kB
Markdown
[CameraKit Web SDK - v0.22.0](../README.md) / [Exports](../modules.md) / CameraKitBootstrapConfiguration
# Interface: CameraKitBootstrapConfiguration
Configuration which must be provided when calling [bootstrapCameraKit](../modules.md#bootstrapcamerakit). These values are used to create various
CameraKit components.
## Table of contents
### Properties
- [apiToken](CameraKitBootstrapConfiguration.md#apitoken)
- [logger](CameraKitBootstrapConfiguration.md#logger)
- [logLevel](CameraKitBootstrapConfiguration.md#loglevel)
- [lensPerformance](CameraKitBootstrapConfiguration.md#lensperformance)
- [lensCoreOverrideUrls](CameraKitBootstrapConfiguration.md#lenscoreoverrideurls)
- [wasmEndpointOverride](CameraKitBootstrapConfiguration.md#wasmendpointoverride)
- [analyticsId](CameraKitBootstrapConfiguration.md#analyticsid)
## Properties
### apiToken
• **apiToken**: `string`
Long-lived token granting your application access to CameraKit APIs. This is found in the SnapKit Dev Portal,
where it's called the API Token.
___
### logger
• `Optional` **logger**: ``"noop"`` \| ``"console"``
Determine where to print CameraKit log messages. By default no logs will be printed.
CameraKit emits log messages to help diagnose and root cause issues that may occur during the development of a
host application. The printing of these can be controlled via the following
options:
- `noop`: log messages are ignored.
- `console`: log messages are printed to console.
___
### logLevel
• `Optional` **logLevel**: ``"error"`` \| ``"warn"`` \| ``"log"`` \| ``"info"`` \| ``"debug"``
Log only if a logged entry level is greater than or equal to this level. Here is the order of levels:
error > warn > log = info > debug. Default value is "info".
___
### lensPerformance
• `Optional` **lensPerformance**: [`EstimatedLensPerformance`](EstimatedLensPerformance.md) \| `Promise`\<[`EstimatedLensPerformance`](EstimatedLensPerformance.md)\>
Some lenses may decide to modify their behavior based on the performance of the current environment. If you are
using such lenses, providing an estimation of lens performance may lead to better user experience (especially on
low-performance devices).
Running the [estimateLensPerformance](../modules.md#estimatelensperformance) function will run benchmarks and estimate an appropriate lens
performance cluster (i.e. a performance rating) based on the current environment.
Lower cluster = worse expected performance capability.
**`Example`**
```ts
import { bootstrapCameraKit, estimateLensPerformance } from '@snap/camera-kit`
const cameraKit = await bootstrapCameraKit({
apiToken: '...',
lensPerformance: estimateLensPerformance(),
})
```
___
### lensCoreOverrideUrls
• `Optional` **lensCoreOverrideUrls**: `Object`
In recommended production deployments, the WebAssembly assets required by CameraKit will be downloaded from an
optimized CDN. But sometimes (e.g. during development or within a CI pipeline), it may be necessary to download
these assets from somewhere else.
This configuration option allows the application to specify URLs to be used for both the WebAssembly and JS glue
file that are used to run and interact with CameraKit's rendering engine.
#### Type declaration
| Name | Type |
| :------ | :------ |
| `wasm` | `string` |
| `js` | `string` |
___
### wasmEndpointOverride
• `Optional` **wasmEndpointOverride**: `string`
In recommended production deployments, the WebAssembly assets required by CameraKit will be downloaded from an
optimized CDN. But sometimes during development or within a CI pipeline, it may be necessary to download these
assets from somewhere else. With a provided `wasmEndpointOverride`, asset URLs will be automatically generated
based on this root endpoint.
___
### analyticsId
• `Optional` **analyticsId**: `string`
Applications may optionally provide a unique identifier called analyticsId. This ID would enable Camera Kit to
improve data reporting and accuracy and to better support potential needs related to an application's lens and
user analytics.