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

chore: transition modules to hybrid ESM/CJS, switch to vitest for testing #7349

Merged
merged 41 commits into from
Nov 4, 2024

Conversation

AlCalzone
Copy link
Member

@AlCalzone AlCalzone commented Oct 31, 2024

closes: #2864

TODO:

@AlCalzone AlCalzone changed the title chore: transition modules to hybrid ESM/CJS chore: transition modules to hybrid ESM/CJS, switch to vitest for testing Nov 1, 2024
@AlCalzone AlCalzone added the infrastructure Issues related to infrastructure and development label Nov 4, 2024
@AlCalzone AlCalzone marked this pull request as ready for review November 4, 2024 09:45
@AlCalzone AlCalzone merged commit 96fbc85 into master Nov 4, 2024
25 checks passed
@AlCalzone AlCalzone deleted the esm-hybrid branch November 4, 2024 09:56
AlCalzone added a commit that referenced this pull request Nov 4, 2024
Z-Wave JS is now released as hybrid ESM/CJS packages.

### Changes under the hood
* Transition modules to hybrid ESM/CJS, switch to vitest for testing (#7349)
AlCalzone added a commit that referenced this pull request Nov 4, 2024
Z-Wave JS is now released as hybrid ESM/CJS packages.

### Changes under the hood
* Transition modules to hybrid ESM/CJS, switch to vitest for testing (#7349)
AlCalzone added a commit that referenced this pull request Nov 5, 2024
In this release, a lot of the internal API was refactored to decrease interdependencies. Technically this results in a huge list of breaking changes, but most of those should not affect any application, unless very low-level APIs are frequently used. For example, Z-Wave JS UI and Z-Wave JS Server had just two small breaks. In addition, Z-Wave JS is now released as hybrid ESM/CJS packages.

### Breaking changes · [Migration guide](https://zwave-js.github.io/node-zwave-js/#/getting-started/migrating/v14)
* `Driver.installConfigUpdates()` now requires the external config directory to be configured (#7365)
* Replace Node.js Buffer with `Uint8Array` portable replacement class `Bytes` (#7332)
* `zwave-js` no longer loops up the package version at runtime (#7344)
* Changed some paths to be relative to `process.cwd()` instead of source location (#7345)
* Decouple CCs and messages from host, split parsing and creation, split ZWaveNode class (#7305)

### Config file changes
* Add Aeotec TriSensor 8 (#7342)

### Changes under the hood
* Decorators have been migrated from the legacy specification to the accepted proposal (#7360)
* Transition modules to hybrid ESM/CJS, switch to vitest for testing (#7349)
* Removed dependency on `fs-extra` in favor of `node:fs/promises` (#7335)
* `@zwave-js/config` no longer loops up the package version at runtime (#7343)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
infrastructure Issues related to infrastructure and development
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant