Releases: NordicSemiconductor/pc-nrfconnect-shared
Releases · NordicSemiconductor/pc-nrfconnect-shared
v126
Fixed
className
property inFileLink
component is now optional
v125
Changed
className
property inFileLink
component is now optional
v124
Added
className
property toFileLink
componentFileLink
will add ellipsis when text overflows
v123
Added
- PID to
nrfutil device
logs when trace is enabled. launcherConfig
to retrieve the launcher config in any renderer process.- Auto select device with
--comPort <path>
. Note this will only select the
device, it will not open a serial connection. App will need to do further
action if it wants to auto open a serial connection as well to that serial
port
Changed
- Analytic events names are now distinct with a prefix of the app name
<AppName>:
e.gnpm:
orppk:
. <App
component no longer provides propertyreportUsageData
and for app
to enable telemetry they must now useusageData.enableTelemetry()
- The function to send telemetry data in
usageData
became async. If you have
to be sure they completed, you now have to await them. getPersistedTerminalSettings
not takes in a device instead of a serial
number and returns undefined for devices with no serial numberpersistTerminalSettings
not takes in a device instead of a serial number
and returns undefined for devices with no serial numberOpenAppOptions
must have serial number or com port path but not both
Fixed
- Serial port in the device list where not aligned correctly
- Auto select device when
--deviceSerial
is provided
Steps to upgrade when using this package
- In
package.json
bumpengines.nrfconnect
to at least>=4.2.2
. - Remove
reportUsageData
property if it is set in project. If this was set
to true addusageData.enableTelemetry()
as shown below. For projects like
launcher addusageData.enableTelemetry()
to main and renderer window. - When using
getPersistedTerminalSettings
replace the serialNumber with the
device in question - When using
persistTerminalSettings
replace the serialNumber with the
device in question s
import React from 'react';
import { App, render } from '@nordicsemiconductor/pc-nrfconnect-shared';
import usageData from '@nordicsemiconductor/pc-nrfconnect-shared/src/utils/usageData';
usageData.enableTelemetry();
render(<App panes={[]} />);
v122
Changed
nrfutil device list
version 2.0.0 no longer probes the device for specific
information to speed up enumeration and hotplug events.- new optional property in device object named
devkit
.jlink
property can be obtained by calling
NrfutilDeviceLib.deviceInfo().jlink
on a Jlink device.hwInfo
property can be obtained by calling
NrfutilDeviceLib.deviceInfo().hwInfo
on a device.dfuTriggerVersion
property can be obtained by calling
NrfutilDeviceLib.deviceInfo().dfuTriggerVersion
on a Nordic DFU device.dfuTriggerInfo
property can be obtained by calling
NrfutilDeviceLib.deviceInfo().dfuTriggerInfo
on a Nordic DFU device
- new optional property in device object named
Added
NrfutilDeviceLib.deviceInfo
to read protocol related device info such as
JLink
andNordicDFU
. Note if no info can be read this will throw (e.g.
mcuboot devices).deviceInfo
is populate automatically when a device is selected and can be
retrieve using the redux selectorselectedDeviceInfo
.
Fixed
- Check installed JLink version against expected version given by nrfutil
(previously this was the version bundled by the launcher).
Steps to upgrade when using this package
- Change
nrfConnectForDesktop.nrfutil.device
to 2.0.0. - Update all device properties to match the changes above.
v121
Added
- NumberInputWithDropdown component, which combines the
NumberInlineInput and the Dropdown components. Example usage found
inBaudrate.tsx
inpc-nrfconnect-serial-terminal
.
Fixed
- Device might end up stuck in device list of left event occurred while we are
waiting for device - Device setup dialog is closed immediately pressing no to programming it
v120
Fixed
prepareSandbox()
couldn't be called from the launcher any longer. Even
when the version to install was provided,prepareSandbox()
tried to look
into thepackage.json
, which didn't exist any longer in the launcher,
because it is only supplied during build time by apps now.
v119
Changed
- Remove default 3000ms timeout from
nrfutil device list
v118
Added
- Option to configure external React to support legacy apps in the launcher.
Changed
- Checking whether the
package.json
contains all required fields is now also
down before building. - Use
zod
for thepackage.json
schema for apps. This is used verify that
apps have the right fields inpackage.json
and also generates the right
TypeScript type for it. nrfConnectForDesktop.html
is not optional anymore, it must always be
specified inpackage.json
.
v117
Fixed
nrfutil device program
did now throw error when files buffers where used