Skip to content
Coveralls

staging changes for cors revamp #393

Sign in to view logs

staging changes for cors revamp

staging changes for cors revamp #393

Triggered via push March 22, 2024 17:39
@kwhitleykwhitley
pushed a11ea47
auto-router-v2-cors
Status Failure
Total duration 31s
Artifacts –

coveralls.yml

on: push
Build
23s
Build
Fit to window
Zoom out
Zoom in

Annotations

5 errors and 1 warning
src/createCors.spec.ts > createCors(options) > OPTIONS > origins should be array of string: src/createCors.spec.ts#L62
AssertionError: expected 'false' to be null // Object.is equality - Expected: null + Received: "false" ❯ src/createCors.spec.ts:62:68
src/createCors.spec.ts > createCors(options) > OPTIONS > origins should be function returns boolean: src/createCors.spec.ts#L77
AssertionError: expected 'false' to be null // Object.is equality - Expected: null + Received: "false" ❯ src/createCors.spec.ts:77:68
src/createCors.spec.ts > createCors(options) > corsify(response: Response): Response > will not modify responses with existing CORS headers: src/createCors.ts#L75
Error: No fetch handler responded and no upstream to proxy to specified. ❯ corsify src/createCors.ts:75:13 ❯ src/createCors.spec.ts:149:24
src/createCors.spec.ts > createCors(options) > corsify(response: Response): Response > will not modify redirects or 101 status responses: src/createCors.ts#L75
Error: No fetch handler responded and no upstream to proxy to specified. ❯ corsify src/createCors.ts:75:13 ❯ src/createCors.spec.ts:159:24
Build
Process completed with exit code 1.
Build
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/setup-node@v3. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.