Skip to content

fix: typecheck

fix: typecheck #227

Triggered via pull request July 1, 2024 06:44
Status Failure
Total duration 11m 25s
Artifacts

checks.yaml

on: pull_request
Fit to window
Zoom out
Zoom in

Annotations

104 errors and 1 warning
Definitions of the following identifiers conflict with those in another file: Type, promises, PathLike, PathOrFileDescriptor, TimeLike, NoParamCallback, BufferEncodingOption, EncodingOption, OpenMode, Mode, Stats, Dirent, Dir, ReadStream, WriteStream, statSync, lstatSync, ReadPosition, WriteFileOptions, WatchEventType, WatchListener, F_OK, R_OK, W_OK, X_OK, COPYFILE_EXCL, COPYFILE_FICLONE, COPYFILE_FICLONE_FORCE, O_RDONLY, O_WRONLY, O_RDWR, O_CREAT, O_EXCL, O_NOCTTY, O_TRUNC, O_APPEND, O_DIRECTORY, O_NOATIME, O_NOFOLLOW, O_SYNC, O_DSYNC, O_SYMLINK, O_DIRECT, O_NONBLOCK, S_IFMT, S_IFREG, S_IFDIR, S_IFCHR, S_IFBLK, S_IFIFO, S_IFLNK, S_IFSOCK, S_IRWXU, S_IRUSR, S_IWUSR, S_IXUSR, S_IRWXG, S_IRGRP, S_IWGRP, S_IXGRP, S_IRWXO, S_IROTH, S_IWOTH, S_IXOTH, UV_FS_O_FILEMAP: .yarn/cache/@types-node-npm-18.16.4-9852dff702-77b58c9acd.zip/node_modules/@types/node/fs.d.ts#L0
Definitions of the following identifiers conflict with those in another file: Type, promises, PathLike, PathOrFileDescriptor, TimeLike, NoParamCallback, BufferEncodingOption, EncodingOption, OpenMode, Mode, Stats, Dirent, Dir, ReadStream, WriteStream, statSync, lstatSync, ReadPosition, WriteFileOptions, WatchEventType, WatchListener, F_OK, R_OK, W_OK, X_OK, COPYFILE_EXCL, COPYFILE_FICLONE, COPYFILE_FICLONE_FORCE, O_RDONLY, O_WRONLY, O_RDWR, O_CREAT, O_EXCL, O_NOCTTY, O_TRUNC, O_APPEND, O_DIRECTORY, O_NOATIME, O_NOFOLLOW, O_SYNC, O_DSYNC, O_SYMLINK, O_DIRECT, O_NONBLOCK, S_IFMT, S_IFREG, S_IFDIR, S_IFCHR, S_IFBLK, S_IFIFO, S_IFLNK, S_IFSOCK, S_IRWXU, S_IRUSR, S_IWUSR, S_IXUSR, S_IRWXG, S_IRGRP, S_IWGRP, S_IXGRP, S_IRWXO, S_IROTH, S_IWOTH, S_IXOTH, UV_FS_O_FILEMAP
Definitions of the following identifiers conflict with those in another file: Type, promises, PathLike, PathOrFileDescriptor, TimeLike, NoParamCallback, BufferEncodingOption, EncodingOption, OpenMode, Mode, Stats, Dirent, Dir, ReadStream, WriteStream, statSync, lstatSync, ReadPosition, WriteFileOptions, WatchEventType, WatchListener, F_OK, R_OK, W_OK, X_OK, COPYFILE_EXCL, COPYFILE_FICLONE, COPYFILE_FICLONE_FORCE, O_RDONLY, O_WRONLY, O_RDWR, O_CREAT, O_EXCL, O_NOCTTY, O_TRUNC, O_APPEND, O_DIRECTORY, O_NOATIME, O_NOFOLLOW, O_SYNC, O_DSYNC, O_SYMLINK, O_DIRECT, O_NONBLOCK, S_IFMT, S_IFREG, S_IFDIR, S_IFCHR, S_IFBLK, S_IFIFO, S_IFLNK, S_IFSOCK, S_IRWXU, S_IRUSR, S_IWUSR, S_IXUSR, S_IRWXG, S_IRGRP, S_IWGRP, S_IXGRP, S_IRWXO, S_IROTH, S_IWOTH, S_IXOTH, UV_FS_O_FILEMAP: .yarn/cache/@types-node-npm-18.16.4-9852dff702-77b58c9acd.zip/node_modules/@types/node/ts4.8/fs.d.ts#L0
Definitions of the following identifiers conflict with those in another file: Type, promises, PathLike, PathOrFileDescriptor, TimeLike, NoParamCallback, BufferEncodingOption, EncodingOption, OpenMode, Mode, Stats, Dirent, Dir, ReadStream, WriteStream, statSync, lstatSync, ReadPosition, WriteFileOptions, WatchEventType, WatchListener, F_OK, R_OK, W_OK, X_OK, COPYFILE_EXCL, COPYFILE_FICLONE, COPYFILE_FICLONE_FORCE, O_RDONLY, O_WRONLY, O_RDWR, O_CREAT, O_EXCL, O_NOCTTY, O_TRUNC, O_APPEND, O_DIRECTORY, O_NOATIME, O_NOFOLLOW, O_SYNC, O_DSYNC, O_SYMLINK, O_DIRECT, O_NONBLOCK, S_IFMT, S_IFREG, S_IFDIR, S_IFCHR, S_IFBLK, S_IFIFO, S_IFLNK, S_IFSOCK, S_IRWXU, S_IRUSR, S_IWUSR, S_IXUSR, S_IRWXG, S_IRGRP, S_IWGRP, S_IXGRP, S_IRWXO, S_IROTH, S_IWOTH, S_IXOTH, UV_FS_O_FILEMAP
Interface 'AssertEntry' cannot simultaneously extend types 'ImportAttribute' and 'Node'.: .yarn/cache/typescript-patch-6e159bfddb-760f7d92fb.zip/node_modules/typescript/lib/typescript.d.ts#L0
Interface 'AssertEntry' cannot simultaneously extend types 'ImportAttribute' and 'Node'. Named property 'kind' of types 'ImportAttribute' and 'Node' are not identical.
Interface 'AssertEntry' cannot simultaneously extend types 'ImportAttribute' and 'Node'.: .yarn/cache/typescript-patch-6e159bfddb-760f7d92fb.zip/node_modules/typescript/lib/typescript.d.ts#L0
Interface 'AssertEntry' cannot simultaneously extend types 'ImportAttribute' and 'Node'. Named property 'parent' of types 'ImportAttribute' and 'Node' are not identical.
Interface 'AssertClause' cannot simultaneously extend types 'ImportAttributes' and 'Node'.: .yarn/cache/typescript-patch-6e159bfddb-760f7d92fb.zip/node_modules/typescript/lib/typescript.d.ts#L0
Interface 'AssertClause' cannot simultaneously extend types 'ImportAttributes' and 'Node'. Named property 'kind' of types 'ImportAttributes' and 'Node' are not identical.
Interface 'AssertClause' cannot simultaneously extend types 'ImportAttributes' and 'Node'.: .yarn/cache/typescript-patch-6e159bfddb-760f7d92fb.zip/node_modules/typescript/lib/typescript.d.ts#L0
Interface 'AssertClause' cannot simultaneously extend types 'ImportAttributes' and 'Node'. Named property 'parent' of types 'ImportAttributes' and 'Node' are not identical.
Type 'typeof import("/home/runner/work/raijin/raijin/.yarn/unplugged/prettier-npm-3.2.5-6859110d6a/node_modules/prettier/plugins/estree")' is not assignable to type 'string | Plugin<any>'.: code/code-format/src/formatter.ts#L42
Type 'typeof import("/home/runner/work/raijin/raijin/.yarn/unplugged/prettier-npm-3.2.5-6859110d6a/node_modules/prettier/plugins/estree")' is not assignable to type 'string | Plugin<any>'.
An import path can only end with a '.ts' extension when 'allowImportingTsExtensions' is enabled.: code/code-lint/src/index.ts#L0
An import path can only end with a '.ts' extension when 'allowImportingTsExtensions' is enabled.
Variable 'hook' implicitly has type 'any' in some locations where its type cannot be determined.: code/code-schematics-worker/src/schematics.worker.content.ts#L3
Variable 'hook' implicitly has type 'any' in some locations where its type cannot be determined.
'Configuration' cannot be used as a value because it was imported using 'import type'.: yarn/pack-utils/src/pack.utils.ts#L76
'Configuration' cannot be used as a value because it was imported using 'import type'.
'Project' cannot be used as a value because it was imported using 'import type'.: yarn/pack-utils/src/pack.utils.ts#L93
'Project' cannot be used as a value because it was imported using 'import type'.
'readonly' type modifier is only permitted on array and tuple literal types.: yarn/workspace-utils/src/get-workspace-dependents.util.ts#L6
'readonly' type modifier is only permitted on array and tuple literal types.
(@typescript-eslint/ban-types): Don't use `Function` as a type. The `Function` type accepts any function-like value. It provides no type safety when calling the function, which can be a common source of bugs. It also accepts things like class declarations, which will throw at runtime as they will not be called with `new`. If you are expecting the function to accept certain arguments, you should explicitly define the function shape.: cli/cli-ui-parts/src/submit-factory.component.tsx#L10
Don't use `Function` as a type. The `Function` type accepts any function-like value. It provides no type safety when calling the function, which can be a common source of bugs. It also accepts things like class declarations, which will throw at runtime as they will not be called with `new`. If you are expecting the function to accept certain arguments, you should explicitly define the function shape.
(@typescript-eslint/ban-types): Don't use `{}` as a type. `{}` actually means "any non-nullish value". - If you want a type meaning "any object", you probably want `object` instead. - If you want a type meaning "any value", you probably want `unknown` instead. - If you want a type meaning "empty object", you probably want `Record<string, never>` instead. - If you really want a type meaning "any non-nullish value", you probably want `NonNullable<unknown>` instead.: code/code-schematics/src/node-pnp-engine.host.ts#L94
Don't use `{}` as a type. `{}` actually means "any non-nullish value". - If you want a type meaning "any object", you probably want `object` instead. - If you want a type meaning "any value", you probably want `unknown` instead. - If you want a type meaning "empty object", you probably want `Record<string, never>` instead. - If you really want a type meaning "any non-nullish value", you probably want `NonNullable<unknown>` instead.
Lint, type check
Process completed with exit code 1.
Lint, type check
Process completed with exit code 1.