Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix: align @types/node with the minimum supported Node.js version #1035

Merged
merged 1 commit into from
Sep 7, 2023

Conversation

AlCalzone
Copy link
Member

This ensures that we don't accidentally use an API that's not available on all supported versions.

@raman325 raman325 merged commit 48d19ef into zwave-js-12 Sep 7, 2023
@raman325 raman325 deleted the types-node-18 branch September 7, 2023 03:40
raman325 added a commit that referenced this pull request Sep 26, 2023
* chore: use vendored tsconfig for Node 18 (#1034)

* fix: align @types/node with the minimum supported Node.js version (#1035)

* fix

* Add support for zwave-js 12 changes (#1036)

* Add support for zwave-js 12 changes

* Bump to b1

* Throw exception if caller uses old parameters for firmware updates

* Tweak parameter name

* additional changes

* Pass error message to clients

* Add friendly name of zwave error code enum to response

* add line break

* throw a zwave error so HA can see the message

* bump to b2

* Review comments

* formatting

* Better backup

* Set prototype in every error type

* Fix error constructor and log a warning instead of throwing an error when enableErrorReporting is called

* Bump to v12

* clean up error messaging logic

* resolve ipv4 first

* Resolve ipv4 first in the client as well

---------

Co-authored-by: AlCalzone <dominic.griesel@nabucasa.com>
raman325 added a commit that referenced this pull request Sep 26, 2023
* chore: use vendored tsconfig for Node 18 (#1034)

* fix: align @types/node with the minimum supported Node.js version (#1035)

* fix

* Bump zwave-js-server to 1.32.0

---------

Co-authored-by: AlCalzone <dominic.griesel@nabucasa.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants