Development and Releases

Development and releases

Requirements

Use Node.js 22 or later. The project has no npm dependencies.

Tests

npm test

The test suite covers discovery, services, editor persistence, Master/Individual conversion, native features, custom header features, layout and localisation.

Development builds

npm run build:dev

The bundle is written to dist/wiser-controls-card.js; metadata is written to dist/build-info.json. A successful development build advances the -dev.N suffix in package.json.

Examples:

• 0.5.1-beta.1-dev.9 → 0.5.1-beta.1-dev.10
• 0.5.1-beta.1 → 0.5.1-beta.2-dev.1
• 0.5.0 → 0.5.1-beta.1-dev.1

Preparing a beta or development release

npm test
npm run build

For a beta development version, the normal build removes the trailing dev component. For example, 0.5.1-beta.1-dev.10 becomes 0.5.1-beta.1.

Commit the generated package version and create the matching tag, such as v0.5.1-beta.1. The release workflow rejects a tag that does not match the semantic package version and attaches wiser-controls-card.js.

Preparing a stable release

Document removed beta aliases as breaking changes in the release announcement.

npm test
npm run build:release

A stable release build removes the beta and development suffix. For example, 0.5.0-beta.4-dev.10 becomes 0.5.0.

Resource URL

Build output reports the cache-busting dashboard resource URL, for example:

/wiser/wiser-controls-card.js?v=0.5.1-beta.1-dev.1

The Wiser integration can consume the built or published asset from this repository.