TypeSpec implementation #5
Draft
Annotations
10 errors and 1 warning
|
Run build script:
src/spec/4.1-structure/4.1.1-service.spec.ts#L44
Cannot find name 'describe'. Do you need to install type definitions for a test runner? Try `npm i --save-dev @types/jest` or `npm i --save-dev @types/mocha`.
|
|
Run build script:
src/spec/4.1-structure/4.1.1-service.spec.ts#L40
Cannot find name 'expect'.
|
|
Run build script:
src/spec/4.1-structure/4.1.1-service.spec.ts#L38
Cannot find name 'expect'.
|
|
Run build script:
src/spec/4.1-structure/4.1.1-service.spec.ts#L25
Cannot find name 'it'. Do you need to install type definitions for a test runner? Try `npm i --save-dev @types/jest` or `npm i --save-dev @types/mocha`.
|
|
Run build script:
src/spec/4.1-structure/4.1.1-service.spec.ts#L24
Cannot find name 'describe'. Do you need to install type definitions for a test runner? Try `npm i --save-dev @types/jest` or `npm i --save-dev @types/mocha`.
|
|
Run build script:
src/spec/4.1-structure/4.1.1-service.spec.ts#L20
Cannot find name 'expect'.
|
|
Run build script:
src/spec/4.1-structure/4.1.1-service.spec.ts#L18
Cannot find name 'expect'.
|
|
Run build script:
src/spec/4.1-structure/4.1.1-service.spec.ts#L5
Cannot find name 'it'. Do you need to install type definitions for a test runner? Try `npm i --save-dev @types/jest` or `npm i --save-dev @types/mocha`.
|
|
Run build script:
src/spec/4.1-structure/4.1.1-service.spec.ts#L4
Cannot find name 'describe'. Do you need to install type definitions for a test runner? Try `npm i --save-dev @types/jest` or `npm i --save-dev @types/mocha`.
|
|
Run build script:
src/spec/4.1-structure/4.1.1-service.spec.ts#L3
Cannot find name 'describe'. Do you need to install type definitions for a test runner? Try `npm i --save-dev @types/jest` or `npm i --save-dev @types/mocha`.
|
|
Complete job
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v3, actions/setup-node@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
Loading