Skip to content

(feat): Enable composition API, enabling easier tailwind usage #8

(feat): Enable composition API, enabling easier tailwind usage

(feat): Enable composition API, enabling easier tailwind usage #8

Triggered via push May 10, 2026 11:01
Status Failure
Total duration 27s
Artifacts

ci.yml

on: push
Fit to window
Zoom out
Zoom in

Annotations

5 errors and 1 warning
ci
Process completed with exit code 1.
src/SplitFlapDisplay.test.tsx > SplitFlapDisplay > character set validation > throws when the value contains a character not in the character set: src/SplitFlapDisplay.test.tsx#L245
AssertionError: expected [Function] to throw error matching /Character "Z" is not in character set…/ but got 'Element type is invalid: expected a s…' - Expected: /Character "Z" is not in character set "AB"/ + Received: "Element type is invalid: expected a string (for built-in components) or a class/function (for composite components) but got: object." ❯ src/SplitFlapDisplay.test.tsx:245:9
src/SplitFlapDisplay.test.tsx > SplitFlapDisplay > character set validation > throws and reports the duplicates when a character set repeats characters: src/SplitFlapDisplay.test.tsx#L237
AssertionError: expected [Function] to throw error matching /duplicate.*A/ but got 'Element type is invalid: expected a s…' - Expected: /duplicate.*A/ + Received: "Element type is invalid: expected a string (for built-in components) or a class/function (for composite components) but got: object." ❯ src/SplitFlapDisplay.test.tsx:237:9
src/SplitFlapDisplay.test.tsx > SplitFlapDisplay > character set validation > throws when one of the per-slot character sets is empty: src/SplitFlapDisplay.test.tsx#L229
AssertionError: expected [Function] to throw error matching /non empty string/ but got 'Element type is invalid: expected a s…' - Expected: /non empty string/ + Received: "Element type is invalid: expected a string (for built-in components) or a class/function (for composite components) but got: object." ❯ src/SplitFlapDisplay.test.tsx:229:9
src/SplitFlapDisplay.test.tsx > SplitFlapDisplay > character set validation > throws when `characters` is an empty string: src/SplitFlapDisplay.test.tsx#L219
AssertionError: expected [Function] to throw error matching /non empty string/ but got 'Element type is invalid: expected a s…' - Expected: /non empty string/ + Received: "Element type is invalid: expected a string (for built-in components) or a class/function (for composite components) but got: object." ❯ src/SplitFlapDisplay.test.tsx:219:9
ci
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-node@v4, pnpm/action-setup@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/