Starts in:
0 DAY
22 HRS
43 MIN
4 SEC
Starts in:
0 D
22 H
43 M
4 S
Open Closed

Problem with microservices template? #3270

User avatar
0
jlavallet created

  • ABP Framework version: v5.3.0

  • UI type:Blazor

  • DB provider: EF Core

  • Tiered (MVC) or Identity Server Separated (Angular): Microservices

  • Exception message and stack trace:

PowerShell 7.2.4
Copyright (c) Microsoft Corporation.

https://aka.ms/powershell
Type 'help' to get help.

Loading personal and system profiles took 516ms.
 passp    ~    ﮫ0ms⠀   abp suite update --p                                   pwsh   100  09:30:32 
[09:31:26 INF] ABP CLI (https://abp.io)
[09:31:27 INF] Version 5.3.0 (Stable)
[09:31:27 INF] Updating ABP Suite to the latest preview version...
Tool 'volo.abp.suite' was successfully updated from version '5.2.2' to version '5.3.0'.
 passp    ~    ﮫ23.854s⠀   abp suite                                                                             pwsh   100  09:31:45 
[09:33:41 INF] ABP CLI (https://abp.io)
[09:33:41 INF] Version 5.3.0 (Stable)
Starting Suite v5.3.0 ...
Opening http://localhost:3000
Press Ctrl+C to shut down.
npm WARN deprecated source-map-resolve@0.5.3: See https://github.com/lydell/source-map-resolve#deprecated
npm WARN deprecated chokidar@2.1.8: Chokidar 2 does not receive security updates since 2019. Upgrade to chokidar 3 with 15x fewer dependencies
npm WARN deprecated urix@0.1.0: Please see https://github.com/lydell/urix#deprecated
npm WARN deprecated resolve-url@0.2.1: https://github.com/lydell/resolve-url#deprecated
npm WARN deprecated source-map-url@0.4.0: See https://github.com/lydell/source-map-url#deprecated
npm WARN deprecated uppy@1.24.0: @uppy/image-editor was missing from package.json, fixed in v1.24.1
npm WARN deprecated flag-icon-css@4.1.7: The project has been renamed to flag-icons

added 510 packages, and audited 511 packages in 50s

11 packages are looking for funding
  run `npm fund` for details

24 vulnerabilities (5 moderate, 16 high, 3 critical)

To address issues that do not require attention, run:
  npm audit fix

To address all issues possible (including breaking changes), run:
  npm audit fix --force

Some issues need review, and may require choosing
a different dependency.

Run `npm audit` for details.
npm WARN deprecated source-map-resolve@0.5.3: See https://github.com/lydell/source-map-resolve#deprecated
npm WARN deprecated chokidar@2.1.8: Chokidar 2 does not receive security updates since 2019. Upgrade to chokidar 3 with 15x fewer dependencies
npm WARN deprecated urix@0.1.0: Please see https://github.com/lydell/urix#deprecated
npm WARN deprecated resolve-url@0.2.1: https://github.com/lydell/resolve-url#deprecated
npm WARN deprecated source-map-url@0.4.0: See https://github.com/lydell/source-map-url#deprecated
npm WARN deprecated flag-icon-css@4.1.7: The project has been renamed to flag-icons

added 411 packages, and audited 412 packages in 30s

11 packages are looking for funding
  run `npm fund` for details

14 vulnerabilities (2 moderate, 12 high)

To address issues that do not require attention, run:
  npm audit fix

To address all issues (including breaking changes), run:
  npm audit fix --force

Run `npm audit` for details.
npm WARN deprecated source-map-resolve@0.5.3: See https://github.com/lydell/source-map-resolve#deprecated
npm WARN deprecated chokidar@2.1.8: Chokidar 2 does not receive security updates since 2019. Upgrade to chokidar 3 with 15x fewer dependencies
npm WARN deprecated urix@0.1.0: Please see https://github.com/lydell/urix#deprecated
npm WARN deprecated resolve-url@0.2.1: https://github.com/lydell/resolve-url#deprecated
npm WARN deprecated source-map-url@0.4.0: See https://github.com/lydell/source-map-url#deprecated
npm WARN deprecated flag-icon-css@4.1.7: The project has been renamed to flag-icons

added 409 packages, and audited 410 packages in 23s

11 packages are looking for funding
  run `npm fund` for details

13 vulnerabilities (2 moderate, 11 high)

To address issues that do not require attention, run:
  npm audit fix

To address all issues (including breaking changes), run:
  npm audit fix --force

Run `npm audit` for details.
npm ERR! code ENOENT
npm ERR! syscall open
npm ERR! path D:\Century\Clients\PigglyWiggly\RPMS\PWADC.GoRPMS\gateways\web-public\src\PWADC.GoRPMS.PublicWebGateway/package.json
npm ERR! errno -4058
npm ERR! enoent ENOENT: no such file or directory, open 'D:\Century\Clients\PigglyWiggly\RPMS\PWADC.GoRPMS\gateways\web-public\src\PWADC.GoRPMS.PublicWebGateway\package.json'
npm ERR! enoent This is related to npm not being able to find a file.
npm ERR! enoent

npm ERR! A complete log of this run can be found in:
npm ERR!     C:\Users\passp\AppData\Local\npm-cache\_logs\2022-06-17T14_42_57_122Z-debug-0.log
npm ERR! code ENOENT
npm ERR! syscall open
npm ERR! path D:\Century\Clients\PigglyWiggly\RPMS\PWADC.GoRPMS\gateways\web\src\PWADC.GoRPMS.WebGateway/package.json
npm ERR! errno -4058
npm ERR! enoent ENOENT: no such file or directory, open 'D:\Century\Clients\PigglyWiggly\RPMS\PWADC.GoRPMS\gateways\web\src\PWADC.GoRPMS.WebGateway\package.json'
npm ERR! enoent This is related to npm not being able to find a file.
npm ERR! enoent

npm ERR! A complete log of this run can be found in:
npm ERR!     C:\Users\passp\AppData\Local\npm-cache\_logs\2022-06-17T14_43_02_325Z-debug-0.log
npm ERR! code ENOENT
npm ERR! syscall open
npm ERR! path D:\Century\Clients\PigglyWiggly\RPMS\PWADC.GoRPMS\services\administration\src\PWADC.GoRPMS.AdministrationService.HttpApi.Host/package.json
npm ERR! errno -4058
npm ERR! enoent ENOENT: no such file or directory, open 'D:\Century\Clients\PigglyWiggly\RPMS\PWADC.GoRPMS\services\administration\src\PWADC.GoRPMS.AdministrationService.HttpApi.Host\package.json'
npm ERR! enoent This is related to npm not being able to find a file.
npm ERR! enoent

npm ERR! A complete log of this run can be found in:
npm ERR!     C:\Users\passp\AppData\Local\npm-cache\_logs\2022-06-17T14_43_07_481Z-debug-0.log
npm ERR! code ENOENT
npm ERR! syscall open
npm ERR! path D:\Century\Clients\PigglyWiggly\RPMS\PWADC.GoRPMS\services\identity\src\PWADC.GoRPMS.IdentityService.HttpApi.Host/package.json
npm ERR! errno -4058
npm ERR! enoent ENOENT: no such file or directory, open 'D:\Century\Clients\PigglyWiggly\RPMS\PWADC.GoRPMS\services\identity\src\PWADC.GoRPMS.IdentityService.HttpApi.Host\package.json'
npm ERR! enoent This is related to npm not being able to find a file.
npm ERR! enoent

npm ERR! A complete log of this run can be found in:
npm ERR!     C:\Users\passp\AppData\Local\npm-cache\_logs\2022-06-17T14_43_12_615Z-debug-0.log
npm ERR! code ENOENT
npm ERR! syscall open
npm ERR! path D:\Century\Clients\PigglyWiggly\RPMS\PWADC.GoRPMS\services\product\src\PWADC.GoRPMS.ProductService.HttpApi.Host/package.json
npm ERR! errno -4058
npm ERR! enoent ENOENT: no such file or directory, open 'D:\Century\Clients\PigglyWiggly\RPMS\PWADC.GoRPMS\services\product\src\PWADC.GoRPMS.ProductService.HttpApi.Host\package.json'
npm ERR! enoent This is related to npm not being able to find a file.
npm ERR! enoent

npm ERR! A complete log of this run can be found in:
npm ERR!     C:\Users\passp\AppData\Local\npm-cache\_logs\2022-06-17T14_43_17_751Z-debug-0.log
npm ERR! code ENOENT
npm ERR! syscall open
npm ERR! path D:\Century\Clients\PigglyWiggly\RPMS\PWADC.GoRPMS\services\product\src\PWADC.GoRPMS.ProductService.Web/package.json
npm ERR! errno -4058
npm ERR! enoent ENOENT: no such file or directory, open 'D:\Century\Clients\PigglyWiggly\RPMS\PWADC.GoRPMS\services\product\src\PWADC.GoRPMS.ProductService.Web\package.json'
npm ERR! enoent This is related to npm not being able to find a file.
npm ERR! enoent

npm ERR! A complete log of this run can be found in:
npm ERR!     C:\Users\passp\AppData\Local\npm-cache\_logs\2022-06-17T14_43_22_930Z-debug-0.log
npm ERR! code ENOENT
npm ERR! syscall open
npm ERR! path D:\Century\Clients\PigglyWiggly\RPMS\PWADC.GoRPMS\services\saas\src\PWADC.GoRPMS.SaasService.HttpApi.Host/package.json
npm ERR! errno -4058
npm ERR! enoent ENOENT: no such file or directory, open 'D:\Century\Clients\PigglyWiggly\RPMS\PWADC.GoRPMS\services\saas\src\PWADC.GoRPMS.SaasService.HttpApi.Host\package.json'
npm ERR! enoent This is related to npm not being able to find a file.
npm ERR! enoent

npm ERR! A complete log of this run can be found in:
npm ERR!     C:\Users\passp\AppData\Local\npm-cache\_logs\2022-06-17T14_43_27_869Z-debug-0.log
  • Steps to reproduce the issue:"

I am running into an issue after using the ABP Suite to generate a microservices solution. During the generation of the solution, I get several errors that indicate that their is no package.json in several of the projects. I have confirmed that these files are missing. I have tried to generate the solution using both ABP Suite v 5.2.2 and ABP Suite v 5.3.0 after upgrading ABP to v 5.3.0 (it should be noticed that I had to use the preview flag to force ABP Suite to upgrade to v5.3.0).

See my Discord post: https://discord.com/channels/951497912645476422/953000230142496789/987375732621717646

Go to accepted answer
2 Answer(s)
  • User Avatar
    0
    yekalkan created
    Support Team Fullstack Developer

    Hi @jlavallet,

    As i see, these logs are harmless and the solution should be created successfully. You can continue development.

    We'll try to remove these logs in the next patch version.

  • User Avatar
    0
    yekalkan created
    Support Team Fullstack Developer

    https://github.com/abpframework/abp/pull/13059

Assignee
User avatar gterdem
Labels
None yet
Made with ❤️ on ABP v9.1.0-preview. Updated on November 20, 2024, 13:06