fix: resolve type errors — narrow undefined access, use Zod schema fo… #2
MearmanAnnotations
14 errors and 3 warnings
|
Typecheck
Process completed with exit code 2.
|
|
Typecheck:
src/bridges/pi/index.ts#L14
Cannot find module 'typebox' or its corresponding type declarations.
|
|
Lint:
src/bridges/pi/index.ts#L127
Unsafe call of a type that could not be resolved
|
|
Lint:
src/bridges/pi/index.ts#L127
Unsafe assignment of an error typed value
|
|
Lint:
src/bridges/pi/index.ts#L123
Unsafe member access .String on a type that cannot be resolved
|
|
Lint:
src/bridges/pi/index.ts#L123
Unsafe call of a type that could not be resolved
|
|
Lint:
src/bridges/pi/index.ts#L122
Unsafe member access .Optional on a type that cannot be resolved
|
|
Lint:
src/bridges/pi/index.ts#L122
Unsafe call of a type that could not be resolved
|
|
Lint:
src/bridges/pi/index.ts#L122
Unsafe assignment of an error typed value
|
|
Lint:
src/bridges/pi/index.ts#L102
Unsafe member access .Object on a type that cannot be resolved
|
|
Lint:
src/bridges/pi/index.ts#L102
Unsafe call of a type that could not be resolved
|
|
Lint:
src/bridges/pi/index.ts#L102
Unsafe assignment of an error typed value
|
|
Test
Process completed with exit code 2.
|
|
Test:
src/bridges/pi/index.ts#L14
Cannot find module 'typebox' or its corresponding type declarations.
|
|
Typecheck
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/
|
|
Lint
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/
|
|
Test
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/
|