Skip to content
Validate

fix(messaging)!: Fix mix up messaging in window and custom event messengers #245

Sign in to view logs

fix(messaging)!: Fix mix up messaging in window and custom event messengers

fix(messaging)!: Fix mix up messaging in window and custom event messengers #245

Triggered via pull request September 15, 2024 14:52
@1natsu1721natsu172
synchronize #70
1natsu172:simple-fix-mixedup
Status Failure
Total duration 1m 38s
Artifacts –

validate.yml

on: pull_request
checks
14s
checks
build
1m 28s
build
tests
28s
tests
Fit to window
Zoom out
Zoom in

Annotations

11 errors and 3 warnings
checks
Process completed with exit code 1.
__tests__/browser/page.test.ts > Window Messenger > should send and return messages: packages/messaging/src/window.ts#L56
ReferenceError: crypto is not defined ❯ defineWindowMessaging window.ts:56:22 ❯ defineTestMessaging __tests__/browser/page.test.ts:22:23 ❯ __tests__/browser/page.test.ts:37:24
__tests__/browser/page.test.ts > Window Messenger > should not send messages to a messenger with a different namespace: packages/messaging/src/window.ts#L56
ReferenceError: crypto is not defined ❯ defineWindowMessaging window.ts:56:22 ❯ defineTestMessaging __tests__/browser/page.test.ts:22:23 ❯ __tests__/browser/page.test.ts:59:24
__tests__/browser/page.test.ts > Window Messenger > should return the first response: packages/messaging/src/window.ts#L56
ReferenceError: crypto is not defined ❯ defineWindowMessaging window.ts:56:22 ❯ defineTestMessaging __tests__/browser/page.test.ts:22:23 ❯ __tests__/browser/page.test.ts:80:24
__tests__/browser/page.test.ts > Window Messenger > should throw an error if the responder throws an error: packages/messaging/src/window.ts#L56
ReferenceError: crypto is not defined ❯ defineWindowMessaging window.ts:56:22 ❯ defineTestMessaging __tests__/browser/page.test.ts:22:23 ❯ __tests__/browser/page.test.ts:106:24
__tests__/browser/page.test.ts > Window Messenger > should be messaging for the same message type between different instances: packages/messaging/src/window.ts#L56
ReferenceError: crypto is not defined ❯ defineWindowMessaging window.ts:56:22 ❯ defineTestMessaging __tests__/browser/page.test.ts:22:23 ❯ __tests__/browser/page.test.ts:121:25
__tests__/browser/page.test.ts > Custom Event Messenger > should send and return messages: packages/messaging/src/custom-event.ts#L62
ReferenceError: crypto is not defined ❯ defineCustomEventMessaging custom-event.ts:62:22 ❯ defineTestMessaging __tests__/browser/page.test.ts:22:23 ❯ __tests__/browser/page.test.ts:37:24
__tests__/browser/page.test.ts > Custom Event Messenger > should not send messages to a messenger with a different namespace: packages/messaging/src/custom-event.ts#L62
ReferenceError: crypto is not defined ❯ defineCustomEventMessaging custom-event.ts:62:22 ❯ defineTestMessaging __tests__/browser/page.test.ts:22:23 ❯ __tests__/browser/page.test.ts:59:24
__tests__/browser/page.test.ts > Custom Event Messenger > should return the first response: packages/messaging/src/custom-event.ts#L62
ReferenceError: crypto is not defined ❯ defineCustomEventMessaging custom-event.ts:62:22 ❯ defineTestMessaging __tests__/browser/page.test.ts:22:23 ❯ __tests__/browser/page.test.ts:80:24
__tests__/browser/page.test.ts > Custom Event Messenger > should throw an error if the responder throws an error: packages/messaging/src/custom-event.ts#L62
ReferenceError: crypto is not defined ❯ defineCustomEventMessaging custom-event.ts:62:22 ❯ defineTestMessaging __tests__/browser/page.test.ts:22:23 ❯ __tests__/browser/page.test.ts:106:24
__tests__/browser/page.test.ts > Custom Event Messenger > should be messaging for the same message type between different instances: packages/messaging/src/custom-event.ts#L62
ReferenceError: crypto is not defined ❯ defineCustomEventMessaging custom-event.ts:62:22 ❯ defineTestMessaging __tests__/browser/page.test.ts:22:23 ❯ __tests__/browser/page.test.ts:121:25
checks
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
tests
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
build
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/