@resin.io/device-types - npm explorer

npm install @resin.io/device-types

Dist Tags

latest10.5.1

s-resin-balena-g-2a49c303942664f7f1dd80420d348465c1d8eb6210.5.0-s-resin-balena-g-2a49c303942664f7f1dd80420d348465c1d8eb62

vipul-etcher-update-962721fc89c309d69be857ff5dcfaab9b4056cef10.5.1-vipul-etcher-update-962721fc89c309d69be857ff5dcfaab9b4056cef

build-alexgg-remove-state-a250f4890517855c17c780424db24773243cfb2a10.5.1-build-alexgg-remove-state-a250f4890517855c17c780424db24773243cfb2a-1

build-alexgg-remove-state10.5.1-build-alexgg-remove-state-a250f4890517855c17c780424db24773243cfb2a-1

This repo holds the common bits used to compose the resin device types info.

Extra Options

Device type can declare extra options needed for the Image Maker.

Options are declared as an array of definitions that partially conform to the Inquirer.js format.

The following option types are recognized at the moment:

* input _(default)_,
* list,
* confirm.

Each client treats these types differently. For example, Web UI renders list as a drop-down and confirm as a checkbox.

The following attributes are supported:

* type – as defined above,
* name — the name of the parameter as it's sent to the Image Maker,
* message — the question / label shown in the UI,
* choices — _for list only_; an array of strings that are possible choices.

For confirm input type the client _should not send any value_ if the question got negative answer (checkbox is unchecked in the UI, or "No" is answered in the CLI), and should send 1 or true otherwise. This behavior could be done more robust (support 0 and false), but that should be changed on the Image Maker side.