@loomhq/record-sdk

See our docs site for a detailed guide on how to use the sdk!

3.2.0

Minor Changes

• bb42d5cf15: Introducing: createInstance, a new setup method for @loomhq/record-sdk

  There are now three operating modes of the SDK:

  • Standard
  • Custom
  • First Party (assumes customer is always authenticated)

  For the sake of simplicity, the developer needs to explicitly say which mode they're using

  // Example
  const publicAppId: '<my public key>';
  
  const instance = await createInstance({
    mode: 'standard',
    publicAppId,
  });

Patch Changes

• 142ef8c30e: Implement foundations for onboarding

• 6a7f688ad8: Navigate to share page edit tab when users are logged in

• 75c95a7853: Add in product name and entry point name into the recording start event

• cf9cde4bb3: Add types export to record-sdk package

• 7e223459ff: Add internal alpha banner for Hello domain

• cf01845b27: Bump Lens v11.9.0 to add small loader

• 3df205aeb9: Be explicit about the different modes the recorder can be in.

  Changes:

  • Deprecate setApiKey action
  • Deprecate setJws action
  • Introduce setMode action

  The recorder can be in one of four modes:

  • PendingSDK (The recorder has been initialized)
  • CustomSDK
  • StandardSDK
  • First-Party

  @loomhq/record-sdk@3.11 and below will continue to use setApiKey and setJws. When these actions are used, sdk-background will transform these actions to be as though setMode was used.

• 7e8de46708: add pre record menu analytics for the sdk

• 211ebf0d1d: Add in product identifier and entry point

• ef1c6c934a: Add changeset

• 6adf796331: Bump Lens to v11.11.0 to add custom height modals

• ad079d01c6: Fixes bug where SDK could not start recording when microphone is disabled