Starts in:
0 DAY
22 HRS
12 MIN
14 SEC
Starts in:
0 D
22 H
12 M
14 S
Open Closed

[Bug] Suite tool stopped generating Angular UI for me #3777


User avatar
0
kirotech created
  • ABP Framework version: v6.0.0-rc.4
  • UI type: Angular
  • DB provider: EF Core
  • Tiered (MVC) or Identity Server Separated (Angular): yes
  • Exception message and stack trace:
  • Steps to reproduce the issue:"

cli version v6.0.0-rc.4 abp suite version v6.0.0-rc.4

Suite just stopped generating ui for me. I tried to update to latest rc version my cli and suite also a project, but after upgrade project stopped working at all so I had to downgrade to make project working again.

This doesn't look like good developer experience at all. I wasted all day on this yesterday trying to recover cli and abp suite also project from failed upgrade.

from abp suite log

2022-09-28 18:50:15.597 +03:00 [INF] Running the Angular Schematics command:
node run-schematics.mjs "C:/project/angular/.suite/schematics/node\_modules/.bin/ng" g ".suite/schematics/collection.json:entity" app-pro Project "C:/project/aspnet-core/.suite/entities/Good.json" "C:/project/angular"
2022-09-28 18:50:30.682 +03:00 [INF] Angular Schematics command failed.
file:///C:/project/angular/.suite/schematics/node\_modules/execa/lib/error.js:59
error = new Error(message);
^

Error: Command failed with exit code 1: .suite/schematics/node\_modules/.bin/ng g .suite/schematics/collection.json:entity app-pro Project C:/project/aspnet-core/.suite/entities/Good.json
this.tree.readText is not a function
at makeError (file:///C:/project/angular/.suite/schematics/node\_modules/execa/lib/error.js:59:11)
at handlePromise (file:///C:/project/angular/.suite/schematics/node\_modules/execa/index.js:119:26)
at processTicksAndRejections (node:internal/process/task\_queues:96:5)
at async file:///C:/project/angular/.suite/schematics/run-schematics.mjs:6:18 {
shortMessage: 'Command failed with exit code 1: .suite/schematics/node\_modules/.bin/ng g .suite/schematics/collection.json:entity app-pro Project C:/project/aspnet-core/.suite/entities/Good.json',
command: '.suite/schematics/node\_modules/.bin/ng g .suite/schematics/collection.json:entity app-pro Project C:/project/aspnet-core/.suite/entities/Good.json',
escapedCommand: '".suite/schematics/node\_modules/.bin/ng" g ".suite/schematics/collection.json:entity" app-pro Project "C:/project/aspnet-core/.suite/entities/Good.json"',
exitCode: 1,
signal: undefined,
signalDescription: undefined,
stdout: '',
stderr: 'this.tree.readText is not a function',
failed: true,
timedOut: false,
isCanceled: false,
killed: false
}

2022\-09\-28 18:50:30\.686 \+03:00 \[INF\] 9/10 \- AngularUiGenerateWithSchematicsCommand completed\. \| Duration: 15091 ms\.\

8 Answer(s)
  • User Avatar
    0
    muhammedaltug created

    Hello,

    Can you retry after removing the angular/.suite folder. If you upgrading to rc.5 please update your project's angular version to 14.

  • User Avatar
    0
    kirotech created

    Tried removing angular/.suite folder number of time already yesterday and it didn't work same error each time. I want to solve this ABP suite UI generation bug first after that I will try to upgrade project to rc5 again.

  • User Avatar
    0
    muhammedaltug created

    Please execute the following command in the angular/.suite/schematics and angular folders and share the results.

    yarn why @abp/ng.schematics
    
    yarn why @angular-devkit/schematics
    
  • User Avatar
    0
    kirotech created
    PS C:\project\angular\.suite\schematics> dotnet tool list -g
    Package Id          Version         Commands
    ---------------------------------------------
    dotnet-ef           6.0.9           dotnet-ef
    volo.abp.cli        6.0.0-rc.4      abp
    volo.abp.suite      6.0.0-rc.4      abp-suite
    PS C:\project\angular\.suite\schematics>
    
    PS C:\project\angular\.suite\schematics> yarn why @abp/ng.schematics
    yarn why v1.22.19
    [1/4] Why do we have the module "@abp/ng.schematics"...?
    [2/4] Initialising dependency graph...
    [3/4] Finding dependency...
    [4/4] Calculating file sizes...
    => Found "@abp/ng.schematics@6.0.0-rc.5"
    info Has been hoisted to "@abp/ng.schematics"
    info This module exists because it's specified in "dependencies".
    info Disk size without dependencies: "96.57MB"
    info Disk size with unique dependencies: "186.89MB"
    info Disk size with transitive dependencies: "268.07MB"
    info Number of shared dependencies: 129
    Done in 4.31s.
    PS C:\project\angular\.suite\schematics>
    
    PS C:\project\angular\.suite\schematics> yarn why @angular-devkit/schematics
    yarn why v1.22.19
    [1/4] Why do we have the module "@angular-devkit/schematics"...?
    [2/4] Initialising dependency graph...
    [3/4] Finding dependency...
    [4/4] Calculating file sizes...
    => Found "@angular-devkit/schematics@11.0.7"
    info Has been hoisted to "@angular-devkit/schematics"
    info Reasons this module exists
       - Specified in "dependencies"
       - Hoisted from "@angular#cli#@angular-devkit#schematics"
       - Hoisted from "@schematics#angular#@angular-devkit#schematics"
       - Hoisted from "@angular#cli#@schematics#update#@angular-devkit#schematics"
    info Disk size without dependencies: "17.28MB"
    info Disk size with unique dependencies: "51.48MB"
    info Disk size with transitive dependencies: "55.56MB"
    info Number of shared dependencies: 29
    => Found "@abp/ng.schematics#@angular-devkit/schematics@14.2.4"
    info Reasons this module exists
       - "@abp#ng.schematics" depends on it
       - Hoisted from "@abp#ng.schematics#@angular#cli#@angular-devkit#schematics"
       - Hoisted from "@abp#ng.schematics#@angular#cli#@schematics#angular#@angular-devkit#schematics"
    info Disk size without dependencies: "872KB"
    info Disk size with unique dependencies: "35.63MB"
    info Disk size with transitive dependencies: "39.34MB"
    info Number of shared dependencies: 30
    Done in 2.33s.
    PS C:\project\angular\.suite\schematics>
    
  • User Avatar
    0
    webking-abp1 created

    I'm having the exact same problem, I made it work with abp suite to generate UIs with angular 14 installed. But then other packages did break.

  • User Avatar
    0
    kirotech created

    Any update on this abp suite bug?

  • User Avatar
    0
    muhammedaltug created

    Hello,

    Can you try the steps below

    • Remove node_modules folders and yan.lock files from angular and angular/.suite/schematics
    • Add the following lines to your package.json
    
    "workspaces": {
        "packages": [
          ".suite/*"
        ],
        "nohoist": [
          "**schematics**",
          "schematics**"
        ]
    },
    "resolutions": {
        "@abp/ng.schematics": "6.0.0-rc.4",
        "@abp/ng.components": "6.0.0-rc.4",
        "@abp/ng.core": "6.0.0-rc.4",
        "@abp/ng.setting-management": "6.0.0-rc.4",
        "@abp/ng.theme.shared": "6.0.0-rc.4",
        "@abp/ng.feature-management": "6.0.0-rc.4",
        "@abp/ng.permission-management": "6.0.0-rc.4",
        "@volo/abp.commercial.ng.ui": "6.0.0-rc.4",
        "@volo/abp.ng.account": "6.0.0-rc.4",
        "@volo/abp.ng.audit-logging": "6.0.0-rc.4",
        "@volo/abp.ng.gdpr": "6.0.0-rc.4",
        "@volo/abp.ng.identity": "6.0.0-rc.4",
        "@volo/abp.ng.openiddictpro": "6.0.0-rc.4",
        "@volo/abp.ng.language-management": "6.0.0-rc.4",
        "@volo/abp.ng.saas": "6.0.0-rc.4",
        "@volo/abp.ng.text-template-management": "6.0.0-rc.4",
        "@volosoft/abp.ng.theme.lepton-x": "1.0.0-rc.5"
    }
    
    • Install packages with yarn command in your angular folder.
    • Try to generate an entity

    Note: Please remember to remove any additional lines from "package.json" when updating to 6.0.0-rc.5 or later versions.

  • User Avatar
    0
    kirotech created

    Can you reset my support tickets count? This is a bug with your abp suite cli not support request i don't think this is fair to count this as tech support request. I fixed the issue with 6.0.0 stable release update.

Made with ❤️ on ABP v9.1.0-preview. Updated on November 20, 2024, 13:06