1) tags-input.e2e.ts:38:7 › tags-input › delete tag by clearing its content and hit enter ──────── Error: Timed out 10000ms waiting for expect(locator).toBeHidden() Locator: locator('[data-testid=vue-tag]') Expected: hidden Received: visible Call log: - expect.toBeHidden with timeout 10000ms - waiting for locator('[data-testid=vue-tag]') 14 × locator resolved to <div dir="ltr" data-value="Vue" data-highlighted="" data-testid="vue-tag" data-scope="tags-input" data-part="item-preview" id="tags-input::R6m::tag:Vue:1">…</div> - unexpected value "visible" at models/tags-input.model.ts:78 76 | 77 | async dontSeeTag(value: string) { > 78 | await expect(this.getTag(value)).toBeHidden() | ^ 79 | } 80 | 81 | async seeInputIsFocused() { at TagsInputModel.dontSeeTag (/home/runner/work/zag/zag/e2e/models/tags-input.model.ts:78:38) at /home/runner/work/zag/zag/e2e/tags-input.e2e.ts:47:13

2) tags-input.e2e.ts:87:7 › tags-input › should navigate tags with arrow keys ──────────────────── Error: Timed out 10000ms waiting for expect(locator).toHaveAttribute(expected) Locator: locator('[data-testid=solid-tag]') Expected string: "" Received string: serializes to the same string Call log: - expect.toHaveAttribute with timeout 10000ms - waiting for locator('[data-testid=solid-tag]') 14 × locator resolved to <div dir="ltr" data-value="Solid" data-testid="solid-tag" data-scope="tags-input" data-part="item-preview" id="tags-input::R6m::tag:Solid:3">…</div> - unexpected value "null" at models/tags-input.model.ts:70 68 | 69 | async seeTagIsHighlighted(value: string) { > 70 | await expect(this.getTag(value)).toHaveAttribute("data-highlighted", "") | ^ 71 | } 72 | 73 | async seeTag(value: string) { at TagsInputModel.seeTagIsHighlighted (/home/runner/work/zag/zag/e2e/models/tags-input.model.ts:70:38) at /home/runner/work/zag/zag/e2e/tags-input.e2e.ts:92:13

The following actions use a deprecated Node.js version and will be forced to run on node20: actions/setup-node@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/