Feat/nestjs validation #111
GitHub Actions / Release
failed
Sep 17, 2024
Errors 2
Found 2 errors
Annotations
Check failure on line 1 in packages/nestjs-grpc-playground/package.json
github-actions / Release
Error release workspace @atls/nestjs-grpc-playground
Exit code 1
Raw output
➤ YN0000: ┌ Library Build
::group::Library Build
➤ YN0000: │ packages/nestjs-grpc-playground/src/index.ts
➤ YN0000: │
➤ YN0000: │ TS283: Relative import paths need explicit file extensions in ECMAScript imports
➤ YN0000: │ when '--moduleResolution' is 'node16' or 'nodenext'. Consider adding an
➤ YN0000: │ extension to the import path.
➤ YN0000: │
➤ YN0000: │
➤ YN0000: │ packages/nestjs-grpc-playground/src/index.ts
➤ YN0000: │
➤ YN0000: │ TS283: Relative import paths need explicit file extensions in ECMAScript imports
➤ YN0000: │ when '--moduleResolution' is 'node16' or 'nodenext'. Consider adding an
➤ YN0000: │ extension to the import path.
➤ YN0000: │
➤ YN0000: │
➤ YN0000: │ packages/nestjs-grpc-playground/src/index.ts
➤ YN0000: │
➤ YN0000: │ TS283: Relative import paths need explicit file extensions in ECMAScript imports
➤ YN0000: │ when '--moduleResolution' is 'node16' or 'nodenext'. Consider adding an
➤ YN0000: │ extension to the import path.
➤ YN0000: │
➤ YN0000: │
➤ YN0000: │ packages/nestjs-grpc-playground/src/index.ts
➤ YN0000: │
➤ YN0000: │ TS283: Relative import paths need explicit file extensions in ECMAScript imports
➤ YN0000: │ when '--moduleResolution' is 'node16' or 'nodenext'. Consider adding an
➤ YN0000: │ extension to the import path.
➤ YN0000: │
➤ YN0000: │
➤ YN0000: │ packages/nestjs-grpc-playground/src/module/grpc-playground-module-options.interf
➤ YN0000: │ ace.ts
➤ YN0000: │
➤ YN0000: │ TS283: Relative import paths need explicit file extensions in ECMAScript imports
➤ YN0000: │ when '--moduleResolution' is 'node16' or 'nodenext'. Consider adding an
➤ YN0000: │ extension to the import path.
➤ YN0000: │
➤ YN0000: │
➤ YN0000: │ packages/nestjs-grpc-playground/src/module/grpc-playground.module.ts
➤ YN0000: │
➤ YN0000: │ TS283: Relative import paths need explicit file extensions in ECMAScript imports
➤ YN0000: │ when '--moduleResolution' is 'node16' or 'nodenext'. Consider adding an
➤ YN0000: │ extension to the import path.
➤ YN0000: │
➤ YN0000: │
➤ YN0000: │ packages/nestjs-grpc-playground/src/module/grpc-playground.module.ts
➤ YN0000: │
➤ YN0000: │ TS283: Relative import paths need explicit file extensions in ECMAScript imports
➤ YN0000: │ when '--moduleResolution' is 'node16' or 'nodenext'. Consider adding an
➤ YN0000: │ extension to the import path.
➤ YN0000: │
➤ YN0000: │
::endgroup::
➤ YN0000: packages/nestjs-grpc-playground/src/index.ts
➤ YN0000:
➤ YN0000: TS283: Relative import paths need explicit file extensions in ECMAScript imports
➤ YN0000: when '--moduleResolution' is 'node16' or 'nodenext'. Consider adding an
➤ YN0000: extension to the import path.
➤ YN0000:
➤ YN0000:
➤ YN0000: packages/nestjs-grpc-playground/src/index.ts
➤ YN0000:
➤ YN0000: TS283: Relative import paths need explicit file extensions in ECMAScript imports
➤ YN0000: when '--moduleResolution' is 'node16' or 'nodenext'. Consider adding an
➤ YN0000: extension to the import path.
➤ YN0000:
➤ YN0000:
➤ YN0000: packages/nestjs-grpc-playground/src/index.ts
➤ YN0000:
➤ YN0000: TS283: Relative import paths need explicit file extensions in ECMAScript imports
➤ YN0000: when '--moduleResolution' is 'node16' or 'nodenext'. Consider adding an
➤ YN0000: extension to the import path.
➤ YN0000:
➤ YN0000:
➤ YN0000: packages/nestjs-grpc-playground/src/index.ts
➤ YN0000:
➤ YN0000: TS283: Relative import paths need explicit file extensions in ECMAScript imports
➤ YN0000: when '--moduleResolution' is 'node16' or 'nodenext'. Consider adding an
➤ YN0000: extension to the import path.
➤ YN0000:
➤ YN0000:
➤ YN0000: packages/nestjs-grpc-playground/src/module/grpc-playground-module-options.interf
➤ YN0000: ace.ts
➤ YN0000:
➤ YN0000: TS283: Relative import paths need explicit file extensions in ECMAScript imports
➤ YN0000: when '--moduleResolution' is 'node16' or 'nodenext'. Consider adding an
➤ YN0000: extension to the import path.
➤ YN0000:
➤ YN0000:
➤ YN0000: packages/nestjs-grpc-playground/src/module/grpc-playground.module.ts
➤ YN0000:
➤ YN0000: TS283: Relative import paths need explicit file extensions in ECMAScript imports
➤ YN0000: when '--moduleResolution' is 'node16' or 'nodenext'. Consider adding an
➤ YN0000: extension to the import path.
➤ YN0000:
➤ YN0000:
➤ YN0000: packages/nestjs-grpc-playground/src/module/grpc-playground.module.ts
➤ YN0000:
➤ YN0000: TS283: Relative import paths need explicit file extensions in ECMAScript imports
➤ YN0000: when '--moduleResolution' is 'node16' or 'nodenext'. Consider adding an
➤ YN0000: extension to the import path.
➤ YN0000:
➤ YN0000:
➤ YN0000: └ Completed in 1s 905ms
➤ YN0000: Failed with errors in 1s 908ms
Check failure on line 1 in packages/nestjs-typeorm-seeding/package.json
github-actions / Release
Error release workspace @atls/nestjs-typeorm-seeding
Exit code 1
Raw output
➤ YN0000: ┌ Library Build
::group::Library Build
➤ YN0000: │ packages/nestjs-typeorm-seeding/src/module/typeorm-seeding.module.ts:4:30
➤ YN0000: │
➤ YN0000: │ TS701: Could not find a declaration file for module 'typeorm'.
➤ YN0000: │ '/home/runner/work/nestjs/nestjs/.yarn/__virtual__/typeorm-virtual-b5d59a77
➤ YN0000: │ cd/2/.yarn/berry/cache/typeorm-npm-0.2.45-8264084ef9-10c0.zip/node_modules/
➤ YN0000: │ typeorm/index.mjs' implicitly has an 'any' type.
➤ YN0000: │ There are types at '/home/runner/work/nestjs/nestjs/.yarn/__virtual__/typ
➤ YN0000: │ eorm-virtual-b5d59a77cd/2/.yarn/berry/cache/typeorm-npm-0.2.45-8264084ef9-1
➤ YN0000: │ 0c0.zip/node_modules/typeorm/index.d.ts', but this result could not be
➤ YN0000: │ resolved when respecting package.json "exports". The 'typeorm' library may
➤ YN0000: │ need to update its package.json or typings.
➤ YN0000: │
➤ YN0000: │ 2 | import { DynamicModule } from '@nestjs/common'
➤ YN0000: │ 3 | import { Module } from '@nestjs/common'
➤ YN0000: │ > 4 | import { Connection } from 'typeorm'
➤ YN0000: │ | ^
➤ YN0000: │ 5 |
➤ YN0000: │ 6 | @Module({})
➤ YN0000: │ 7 | export class TypeOrmSeedingModule {
➤ YN0000: │
➤ YN0000: │
::endgroup::
➤ YN0000: packages/nestjs-typeorm-seeding/src/module/typeorm-seeding.module.ts:4:30
➤ YN0000:
➤ YN0000: TS701: Could not find a declaration file for module 'typeorm'.
➤ YN0000: '/home/runner/work/nestjs/nestjs/.yarn/__virtual__/typeorm-virtual-b5d59a77
➤ YN0000: cd/2/.yarn/berry/cache/typeorm-npm-0.2.45-8264084ef9-10c0.zip/node_modules/
➤ YN0000: typeorm/index.mjs' implicitly has an 'any' type.
➤ YN0000: There are types at '/home/runner/work/nestjs/nestjs/.yarn/__virtual__/typ
➤ YN0000: eorm-virtual-b5d59a77cd/2/.yarn/berry/cache/typeorm-npm-0.2.45-8264084ef9-1
➤ YN0000: 0c0.zip/node_modules/typeorm/index.d.ts', but this result could not be
➤ YN0000: resolved when respecting package.json "exports". The 'typeorm' library may
➤ YN0000: need to update its package.json or typings.
➤ YN0000:
➤ YN0000: 2 | import { DynamicModule } from '@nestjs/common'
➤ YN0000: 3 | import { Module } from '@nestjs/common'
➤ YN0000: > 4 | import { Connection } from 'typeorm'
➤ YN0000: | ^
➤ YN0000: 5 |
➤ YN0000: 6 | @Module({})
➤ YN0000: 7 | export class TypeOrmSeedingModule {
➤ YN0000:
➤ YN0000:
➤ YN0000: └ Completed in 2s 115ms
➤ YN0000: Failed with errors in 2s 119ms
Loading