Repository navigation
Releases: niklv/node-red-contrib-daichi-cloud
Releases · niklv/node-red-contrib-daichi-cloud
Release list
v2.0.0
Requires Node-RED 5.0 and Node.js 22. The package is now an ES module, which Node-RED 5 loads through dynamic import.
Breaking
- Minimum Node-RED is 5.0, minimum Node.js is 22.
- The package ships as an ES module. Node-RED 4 and earlier cannot load it.
Fixed
- An mqtt socket error had no listener and could take down the whole Node-RED runtime. The broker connection is now guarded.
- Device discovery posted to an absolute url, so Node-RED attached neither the admin root nor the auth token. It now uses a relative url and works behind
httpAdminRootand withadminAuth. - An account filled in but not yet deployed could not list its devices. The editor now sends its credentials with the discovery request.
- Failed logins, unreadable notifications, unreachable devices and a missing account are reported through the node with a status, instead of
consoleoutput or an unhandled rejection. - A broker connection opened after the node closed is now ended instead of leaking, and a closed node no longer publishes device state.
- One failing listener no longer stops the other devices in a notification from updating, nor gets reported as a malformed payload.
- A slow initial read no longer overwrites fresher broker updates, and the state object is copied before it is sent, so downstream nodes cannot corrupt it.
- The discover endpoint is behind
RED.auth.needsPermissionand answers 400 for missing credentials, 502 with the cloud's own message.
Changed
- Built with tsdown. Each node is a standalone bundle; each editor script is inlined into its edit dialog.
- oxlint and oxfmt replace prettier.
- Tests run on
node-red-node-test-helperunder vitest, covering both nodes and the admin endpoint. - The example flow now ships with the package and appears under Import, Examples.
- Published through npm trusted publishing, with provenance.