DocumentationDevice interactionIntegration WalkthroughsMigrationsDevice Management Kitv0.5.0 -> 0.6.0

Migration from 0.5.0 to 0.6.0

We made some breaking changes to the Device Management Kit in 0.6 which are detailed below.

Transports

The transports implementation have been moved to their own packages.

  • @ledgerhq/device-transport-kit-web-hid
  • @ledgerhq/device-transport-kit-web-ble

To use a transport, you need to install the corresponding package and inject it in the DeviceManagementKit.

DMK v0.5

Transports were built-in the DeviceManagementKit.

import {
  DeviceManagementKitBuilder,
  ConsoleLogger,
} from "@ledgerhq/device-management-kit";
 
const dmk = new DeviceManagementKitBuilder()
  .addLogger(new ConsoleLogger())
  .build();

DMK v0.6

In v0.6, you need to manually inject the transport you want to use.

import {
  DeviceManagementKitBuilder,
  ConsoleLogger,
} from "@ledgerhq/device-management-kit";
import { webHidTransportFactory } from "@ledgerhq/device-transport-kit-web-hid";
 
const dmk = new DeviceManagementKitBuilder()
  .addLogger(new ConsoleLogger())
  .addTransport(webHidTransportFactory)
  .build();
import { DeviceManagementKitBuilder, ConsoleLogger } from "@ledgerhq/device-management-kit";
+ import { webHidTransportFactory } from "@ledgerhq/device-transport-kit-web-hid";
 
const dmk = new DeviceManagementKitBuilder()
  .addLogger(new ConsoleLogger())
+ .addTransport(webHidTransportFactory)
  .build();
Ledger
Copyright © Ledger SAS. All rights reserved. Ledger, Ledger Nano S, Ledger Vault, Ledger OS are registered trademarks of Ledger SAS