Unable to Download LeptonX Theme Source Code

Hello ABP Team,

I am unable to download the source code for Volo.Abp.LeptonXTheme.

I have already verified that I am signed in with the correct ABP account and organization.

I can successfully download the source code for all other commercial modules. The issue only occurs with LeptonX Theme.

I also tried downloading it using the ABP CLI:

abp get-source Volo.Abp.LeptonXTheme --version 10.5.0

The command starts downloading the module but fails with the following exception:

Volo.Abp.Studio.AbpStudioException:
Downloading source code failed for: Volo.Abp.LeptonXTheme

Could you please verify whether my account/organization has the correct entitlement for the LeptonX Theme source code, or if there is any issue with the download service for this module?

Thank you.

Unable to Download LeptonX Theme Pro Source Code from ABP Studio

Hello ABP Support,

I am experiencing an issue accessing the LeptonX Theme Pro source code through ABP Studio.

I have successfully downloaded and accessed the source code for all the other commercial modules using ABP Studio. However, LeptonX Theme Pro is the only module that I cannot access.

When I open the module, ABP Studio displays the following message:

You don't have access to the source code of this module.

I am using ABP Studio (not the ABP CLI), and all other commercial modules are working as expected. This issue appears to be specific to Volo.Abp.LeptonXTheme.Pro.

Environment

• ABP Framework: 10.5.0
• ABP Studio: 3.0.6
• Module: Volo.Abp.LeptonXTheme.Pro

Could you please verify whether my account or organization has the required entitlement to access the LeptonX Theme Pro source code? If my subscription includes it, please advise how I can download it through ABP Studio.

Thank you for your assistance.

Unable to Access LeptonX Theme Source Code

Hello ABP Support, I have an active ABP Commercial subscription with Source Code access. I have successfully downloaded and accessed the source code for all the other commercial modules without any issues. However, I am unable to access the source code for Volo.Abp.LeptonXTheme. When I open the module in ABP Studio, I receive the following message:

You don't have access to the source code of this module. Since I can access the source code for all the other commercial modules, it appears that the issue is specific to the LeptonX Theme module. Could you please verify whether my account has the required permission to access the LeptonX Theme source code? If my subscription includes it, please let me know how I can download or add it to my solution.

Environment

• ABP Framework: 10.5.0
• ABP Studio: 3.0.6
• Module: Volo.Abp.LeptonXTheme

Thank you for your support.

Angular Compiler Error (TS2307) after Downloading Account.Pro Source Code (v10.4.1)

Message

Hi ABP Support Team,

I am facing a blocker with the Angular application in my ABP Commercial project (v10.4.1) after downloading the source code for the Volo.Abp.Account.Pro module.

🚨 The Issue

When running the Angular compiler (npm start or ng build), it fails with the following error inside the newly downloaded module projects:

X [ERROR] TS2307: Cannot find module '@abp/ng.core' or its corresponding type declarations. [plugin angular-compiler]

  ../modules/Volo.Abp.Account.Pro/angular/projects/account/admin/config/src/account-admin-config.module.ts:1:27:
    1 │ import { CoreModule } from '@abp/ng.core';

📂 Context & Configuration

ABP Version

• 10.4.1 (Commercial)

Current Situation

I have other local modules (e.g., a custom finance module) under the ../modules/ directory, and they are working completely fine without any compilation or path mapping issues.

Module Structure

The downloaded Volo.Abp.Account.Pro module contains a projects folder with account and account.core. Each sub-project contains its own isolated tsconfig.lib.json which has:

{
  "types": []
}

and extends from a local base configuration.

Main Application tsconfig.json

{
  "compileOnSave": false,
  "compilerOptions": {
    "baseUrl": "./",
    "outDir": "./dist/out-tsc",
    "sourceMap": true,
    "declaration": false,
    "esModuleInterop": true,
    "experimentalDecorators": true,
    "moduleResolution": "bundler",
    "importHelpers": true,
    "skipLibCheck": true,
    "target": "ES2022",
    "module": "ES2022",
    "paths": {
      "@volo/abp.ng.account": [
        "../modules/Volo.Abp.Account.Pro/angular/projects/account/src/public-api.ts"
      ],
      "@volo/abp.ng.account/admin": [
        "../modules/Volo.Abp.Account.Pro/angular/projects/account/admin/src/public-api.ts"
      ],
      "@volo/abp.ng.account/public": [
        "../modules/Volo.Abp.Account.Pro/angular/projects/account/public/src/public-api.ts"
      ],
      "@volo/abp.ng.account/admin/config": [
        "../modules/Volo.Abp.Account.Pro/angular/projects/account/admin/config/src/public-api.ts"
      ],
      "@volo/abp.ng.account/public/config": [
        "../modules/Volo.Abp.Account.Pro/angular/projects/account/public/config/src/public-api.ts"
      ],
      "@volo/abp.ng.account/public/proxy": [
        "../modules/Volo.Abp.Account.Pro/angular/projects/account/public/proxy/src/public-api.ts"
      ],
      "@volo/abp.ng.account.core": [
        "../modules/Volo.Abp.Account.Pro/angular/projects/account.core/src/public-api.ts"
      ]
    },
    "useDefineForClassFields": false
  }
}

🛠️ What I Have Tried So Far

1. Explicitly mapped @abp/ng.core to target the root node_modules/@abp/ng.core inside the main tsconfig.json.
2. Cleared the .angular cache folder and rebuilt/reinstalled node_modules.
3. Modified the sub-project's internal tsconfig.json files to resolve paths manually.

However, the isolated compilation structure of Account Pro combined with "moduleResolution": "bundler" prevents it from tracking the global packages correctly.

❓ Question

Since this issue is isolated strictly to the Account Pro workspace architecture and does not affect my other source-code modules, could you please guide me on the official/correct way to resolve:

• Path mappings for ABP Angular packages within downloaded commercial modules.
• Required peer dependencies for Account Pro source-code projects.
• Any additional workspace configuration needed when integrating the module into an existing Angular application.

Any guidance would be greatly appreciated.

Best regards,

Abdulsalm Alshuaibi