Activities of "pradeep.pradyumna"

[maliming] said: Hi,

Angular CDK 22 opens MatDialog in the browser's top layer by default (it uses the native popover API). Elements outside the top layer always stay behind it, so abp-modal can't get above the dialog with z-index alone, even with 10001.

You can turn this off in your root providers:

import { OVERLAY_DEFAULT_CONFIG } from '@angular/cdk/overlay'; 
 
export const appConfig: ApplicationConfig = { 
  providers: [ 
    // ...your existing providers 
    { provide: OVERLAY_DEFAULT_CONFIG, useValue: { usePopover: false } }, 
  ], 
}; 

This puts all CDK overlays back to normal z-index stacking.

After that, your windowClass / backdropClass workaround works. You don't need ::ng-deep, just put the CSS in the global styles.scss. Use a more specific selector than the rules in dark.css. Otherwise the result depends on which file loads last.

<abp-modal 
  [(visible)]="openViewDocument" 
  [options]="{ windowClass: 'above-cdk-overlay', backdropClass: 'above-cdk-overlay-backdrop' }" 
> 
  ... 
</abp-modal> 
body ngb-modal-backdrop.modal-backdrop.above-cdk-overlay-backdrop { 
  z-index: 10001 !important; 
} 
 
body ngb-modal-window.modal.above-cdk-overlay { 
  z-index: 10002 !important; 
} 

If the delete confirmation comes from ABP's ConfirmationService, it isn't an ng-bootstrap modal, so these classes don't apply to it. Add this to the global styles as well:

body .confirmation { 
  z-index: 10003 !important; 
} 

The [options] input is typed as NgbModalOptions and is passed to NgbModal.open() as is, so container and the other ng-bootstrap options work too: https://abp.io/docs/latest/framework/ui/angular/modal#options

About abpBody: abp-modal already used the signal contentChild('abpBody') in 8.3.0, the same query as in 10.6. Your original markup with two <ng-template *ngIf="..." #abpBody> also renders the right body with ABP 10.6.0 and Angular 22.1, so the empty body comes from something else on that page. Your single #abpBody version is fine to keep. If you want us to look into the original one, please share a small project that reproduces it.

Thanks

This worked! Thank you!

[AI-Bot] said:

  • Issue 1 (z-index / MatDialog overlay): abp-modal is implemented on top of ng-bootstrap’s NgbModal, which appends ngb-modal-window / ngb-modal-backdrop to document.body. When your app (or theme) sets .cdk-overlay-container { z-index: 10000 !important; } and ng-bootstrap modal/backdrop stays at a lower z-index (e.g., 9999), the modal will render behind the CDK overlay stack.
    Supported ABP-side workaround (no need to fork ABP): pass windowClass / backdropClass via the [options] input (ABP spreads options() into NgbModal.open(...)), then override z-index globally.
<abp-modal 
    [(visible)]="openViewDocument" 
    [options]="{ 
      windowClass: 'abp-above-cdk', 
      backdropClass: 'abp-above-cdk-backdrop' 
    }" 
  > 
    <ng-template #abpBody>...</ng-template> 
  </abp-modal> 

Put the CSS in a global stylesheet (recommended), so you don’t need ::ng-deep:

ngb-modal-window.abp-above-cdk { z-index: 10001 !important; } 
  ngb-modal-backdrop.abp-above-cdk-backdrop { z-index: 10001 !important; } 

Notes:

  • Using a component-scoped stylesheet forces you into ::ng-deep because the modal elements are not inside the component’s DOM tree (they’re appended to body).
  • Your current CSS values confirm the root cause: 9999 < 10000, so it will always lose against .cdk-overlay-container. >
  • Issue 2 (contentChild('abpBody') + *ngIf on <ng-template>): In ABP 10.6, abp-modal uses Angular’s signal-based contentChild('abpBody'). That query will not reliably find a template reference that is structurally wrapped (like <ng-template *ngIf ... #abpBody>), because *ngIf on an <ng-template> creates an additional outer template layer.
    Fix in application code: keep exactly one projected <ng-template #abpBody> and move conditional logic inside it (as you already did):
<abp-modal [(visible)]="showModal"> 
    <ng-template #abpBody> 
      <app-edit-form *ngIf="isEditMode"></app-edit-form> 
      <app-view-only *ngIf="!isEditMode"></app-view-only> 
    </ng-template> 
  </abp-modal> 

This pattern aligns with how ABP’s modal is documented/used (single #abpBody template projected into the component).

  • About your requested ABP changes (what is verifiable from sources):
    • From the ABP Angular modal docs, the modal is expected to be used by projecting #abpHeader/#abpBody/#abpFooter templates (single templates) into <abp-modal>. Your “two #abpBody templates toggled by *ngIf” is not a documented usage pattern, and it becomes fragile with signal-based content queries.
    • There is no verified, official ABP documentation (in the retrieved sources) that mentions a zIndex input, container option, or a migration note specifically about contentChild() + *ngIf on <ng-template #abpBody>.

Sources (verified)

  • https://abp.io/docs/latest/framework/ui/angular/modal
  • https://github.com/abpframework/abp/blob/dev/npm/ng-packs/packages/theme-shared/src/lib/components/modal/modal.component.ts
  • https://github.com/abpframework/abp/tree/dev/npm/ng-packs/packages/theme-shared

This response was generated by AI. If it didn’t solve your problem, feel free to post a new answer — our support team will jump in to help you soon.

No AI response, please!

I applied the changes, I still see the abp-modal appears begin the custom pop-up. you can refer to the screenshot below

ABP Support Ticket: abp-modal z-index and contentChild Issues After ABP 10.6 + Angular 22 Upgrade

Date: 2026-10-27 Product: ABP Commercial (Angular UI) ABP Version: 10.6.0 Angular Version: 22.1.4 Affected Package: @abp/ng.theme.shared v10.6.0 Priority: High Related JIRA Tickets: VL-246XX (Issue 4), VL-246XX


1. Executive Summary

After upgrading from ABP 8.3 + Angular 17 to ABP 10.6 + Angular 22, <abp-modal> exhibits two critical issues when used inside components that are themselves opened as Angular Material (MatDialog) or CDK overlay-based dialogs:

  1. Z-index stacking conflict: The abp-modal (ng-bootstrap modal) renders behind the CDK overlay container, making it invisible/inaccessible to the user.
  2. contentChild('abpBody') signal query fails: When <ng-template #abpBody> is conditionally wrapped with *ngIf, ABP 10.6's new signal-based contentChild() query cannot find the template reference, resulting in an empty modal body.

These issues did not exist in ABP 8.3 + Angular 17. They are regressions introduced by the ABP 10.6 migration to Angular Signals-based content queries and the interaction between ng-bootstrap's modal z-index and CDK overlay z-index.


2. Upgrade Context

2.1 Project Background

TASConnect Litmus is a multi-tenant Supply Chain Finance (SCF) and Trade Finance SaaS platform. The upgrade was a full-stack migration:

| Component | Before | After | |-----------|--------|-------| | Angular | 17.3.12 | 22.1.4 | | ABP Framework (Angular) | 8.3.0 | 10.6.0 | | ABP Framework (.NET) | 8.3.1 | 10.6.0 | | TypeScript | 5.3.0 | 6.0.0 | | .NET | 8.0 | 10.0 | | Angular Material | 17.3.10 | 22.1.4 | | Angular CDK | 17.3.10 | 22.1.4 | | ng-bootstrap | 16.0.0 | 21.0.0 | | ng-zorro-antd | 17.4.1 | 22.0.1 |

2.2 Upgrade Scale

740 files modified, ~738 components updated, 50+ DTOs fixed, 17 modules refactored, 272 .csproj files updated on backend.


3. Issue 1: abp-modal Appears Behind CDK Overlay (Z-index Conflict)

3.1 Description

When <abp-modal> is used inside a component that is itself opened as a MatDialog (Angular Material dialog), the abp-modal renders behind the MatDialog overlay and is completely inaccessible to the user. The user sees the parent dialog but cannot see or interact with the abp-modal that should appear on top.

3.2 JIRA References

  • VL-246XX (Issue 4): "The document screen opens behind the Batch details screen and user won't be able to see it."
    • Flow: Payment In Progress tab → View Batch (Actions) → Batch Details dialog → Click "View documents" → abp-modal should show documents on top → abp-modal appears behind
  • VL-246XX: "Delete Documents confirmation popup appears behind the upload screen"
    • Flow: Supply Chain Financing → View Documents → Click Delete icon → Confirmation popup appears behind upload screen

3.3 Steps to Reproduce

  1. Open a component as a MatDialog (CDK overlay-based dialog)
  2. Inside that dialog, trigger an <abp-modal> to open (e.g., click "View Documents")
  3. Expected: abp-modal appears on top of the MatDialog
  4. Actual: abp-modal appears behind the MatDialog and is inaccessible

3.4 Root Cause Analysis

The issue is a z-index conflict between three CSS systems:

CDK Overlay Container (Angular Material)

The application's global stylesheet (dark.css) sets the CDK overlay container z-index:

/* dark.css, line 1163 */
.cdk-overlay-container {
  z-index: 10000 !important;
  left: 0px !important;
  position: fixed !important;
}

ng-bootstrap Modal (ABP's modal backend)

The application's global stylesheet also sets ng-bootstrap modal z-index:

/* dark.css, line 3340-3348 */
ngb-modal-backdrop.modal-backdrop {
  z-index: 9999 !important;
  transition: none !important;
}

ngb-modal-window.modal {
  z-index: 9999 !important;
  transition: none !important;
}

ng-bootstrap Backdrop Inline Style

Additionally, NgbModalBackdrop has a hardcoded inline style in its @Component host metadata:

// @ng-bootstrap/ng-bootstrap - NgbModalBackdrop component
@Component({
  selector: 'ngb-modal-backdrop',
  host: {
    '[class]': '"modal-backdrop" + (backdropClass ? " " + backdropClass : "")',
    style: 'z-index: 1055',  // ← Hardcoded inline style
  },
})

The Conflict

| Layer | Element | z-index | Source | |-------|---------|---------|--------| | CDK overlay container | .cdk-overlay-container | 10000 !important | dark.css line 1163 | | ng-bootstrap modal window | ngb-modal-window.modal | 9999 !important | dark.css line 3345 | | ng-bootstrap modal backdrop | ngb-modal-backdrop.modal-backdrop | 9999 !important | dark.css line 3340 | | ng-bootstrap backdrop inline | ngb-modal-backdrop | 1055 | Hardcoded host style |

Since 9999 < 10000, the ng-bootstrap modal (used by abp-modal) always renders behind the CDK overlay container (used by MatDialog). This means any abp-modal opened from within a MatDialog is invisible.

In ABP 8.3 + Angular 17, this was not an issue because:

  • The older Angular Material (v17) CDK overlay had different z-index defaults
  • The application did not have the same z-index escalation in global CSS
  • The ng-bootstrap version (16.x) may have had different stacking behavior

3.5 ABP ModalComponent Source Analysis

From @abp/ng.theme.shared v10.6.0 (fesm2022 bundle), the ModalComponent.toggle() method:

// @abp/ng.theme.shared - ModalComponent.toggle() (line ~1826) — simplified
this.modalRef = this.modal.open(this.modalContent(), {
    size: 'md', centered: false, keyboard: false, scrollable: true,
    ...this.options(),  // ← Spreads user options to ng-bootstrap
    windowClass: `${this.options().windowClass || ''} ${this.modalIdentifier}`,
});

this.options() is spread into ng-bootstrap's modal.open(). This means windowClass and backdropClass from [options] input pass through to ng-bootstrap. This is the only mechanism to influence the modal's z-index from the consumer side.

3.6 Why ABP Should Address This

  1. abp-modal does not expose any z-index configuration — consumers cannot set z-index through the component API.
  2. ng-bootstrap appends modal elements to document.body — outside the component's view encapsulation, making scoped CSS impossible without ::ng-deep.
  3. The ng-bootstrap backdrop has a hardcoded inline style: 'z-index: 1055' — this cannot be overridden by CSS classes without !important.
  4. CDK overlay + ng-bootstrap modal is a common combination — many ABP applications use both Angular Material and ABP's modal system. ABP should provide a supported way to handle z-index stacking when these systems coexist.

3.7 Our Workaround

We pass custom CSS classes via [options] and use ::ng-deep with !important to override z-index:

<!-- alert.component.html -->
<abp-modal
  [options]="{
    size: 'md',
    windowClass: 'above-cdk-overlay',
    backdropClass: 'above-cdk-overlay-backdrop'
  }"
  [(visible)]="openViewDocument"
>
  <!-- modal content -->
</abp-modal>
/* alert.component.scss */
::ng-deep ngb-modal-window.above-cdk-overlay {
    z-index: 10001 !important;
}

::ng-deep ngb-modal-backdrop.above-cdk-overlay-backdrop {
    z-index: 10001 !important;
}

Problems with this workaround:

  • Requires ::ng-deep (deprecated in Angular, may be removed in future versions)
  • Requires !important to override both the stylesheet rule and inline style
  • Must be applied individually to every <abp-modal> that could appear above a CDK overlay
  • Not discoverable — had to read ABP source code to find that [options] passes through to ng-bootstrap

3.8 Suggested Fix from ABP

  1. Add a zIndex input to ModalComponent that sets z-index on both the modal window and backdrop.
  2. Add a container option that allows specifying a container element (ng-bootstrap supports this). If the modal could be appended inside the CDK overlay container, it would inherit the CDK z-index context.
  3. Document the windowClass/backdropClass passthrough — this is currently undocumented but is the only workaround available.
  4. Consider using CDK overlay instead of ng-bootstrap for modal rendering, since ABP already depends on @angular/cdk. This would eliminate the z-index conflict entirely.

4. Issue 2: contentChild('abpBody') Signal Query Fails with *ngIf on <ng-template>

4.1 Description

ABP 10.6's ModalComponent uses Angular Signals-based contentChild() queries:

// @abp/ng.theme.shared v10.6.0 - ModalComponent
this.abpBody = contentChild('abpBody', /* ... */);

In ABP 8.3, this was a @ContentChild decorator-based query. The migration to contentChild() signal introduces a breaking behavioral change when *ngIf is used on <ng-template>.

4.2 Code Pattern That Breaks

This pattern worked in ABP 8.3 + Angular 17 but breaks in ABP 10.6 + Angular 22:

<!-- BROKEN in ABP 10.6 + Angular 22 -->
<abp-modal [(visible)]="openViewDocument">
  <ng-template *ngIf="!isFxPayModule" #abpBody>
    <app-component-a [IsViewOnly]="true"></app-component-a>
  </ng-template>
  <ng-template *ngIf="isFxPayModule" #abpBody>
    <app-component-b [IsViewOnly]="false"></app-component-b>
  </ng-template>
</abp-modal>

4.3 Root Cause

In Angular 22, *ngIf is syntactic sugar for an implicit <ng-template> wrapper. When *ngIf is placed on a <ng-template>, Angular creates a nested template structure:

<!-- What Angular 22 actually creates: -->
<ng-template [ngIf]="!isFxPayModule">
  <ng-template #abpBody>
    <app-component-a></app-component-a>
  </ng-template>
</ng-template>

The #abpBody template reference is now inside an outer *ngIf template. Angular's contentChild() signal query searches the direct content children of the component. Since #abpBody is wrapped inside the *ngIf template, it's no longer a direct content child — contentChild('abpBody') returns undefined.

ABP's ModalComponent template uses:

<!-- ABP ModalComponent template -->
@if (abpBody()) {
  <div id="abp-modal-body" class="modal-body">
    <ng-container *ngTemplateOutlet="abpBody()"></ng-container>
  </div>
}

Since abpBody() is undefined, the @if block evaluates to false, and the modal body is never rendered — the modal opens but appears empty.

4.4 Our Workaround

Consolidate into a single <ng-template #abpBody> and move the *ngIf to the child components:

<!-- WORKING in ABP 10.6 + Angular 22 -->
<abp-modal [(visible)]="openViewDocument">
  <ng-template #abpBody>
    <app-component-a *ngIf="!isFxPayModule" [IsViewOnly]="true"></app-component-a>
    <app-component-b *ngIf="isFxPayModule" [IsViewOnly]="false"></app-component-b>
  </ng-template>
</abp-modal>

4.5 Why This Is a Breaking Change from ABP

  1. ABP 8.3 used @ContentChild decorator which could find #abpBody even when wrapped in structural directives in some cases, or the pattern was resilient to it.
  2. ABP 10.6 switched to contentChild() signal which has stricter matching behavior for content projection.
  3. This is not documented in ABP 10.6 migration guide — there is no mention that *ngIf on <ng-template #abpBody> will break.
  4. The pattern of conditionally showing different modal bodies is common — many applications use *ngIf to switch between view/edit modes, different user roles, etc.

4.6 Suggested Fix from ABP

  1. Document this breaking change in the ABP 8.x → 10.x migration guide with clear examples.
  2. Consider using contentChildren() (plural) with a filter, or @ContentChild with { descendants: true } equivalent, to find #abpBody even when wrapped in structural directives.
  3. Add a runtime warning when abpBody() returns undefined but the modal is visible — this would help developers diagnose the issue faster.

5. Environment Details

5.1 Package Versions (from package.json)

{
  "@angular/core": "~22.1.4",
  "@angular/material": "~22.1.4",
  "@angular/cdk": "~22.1.4",
  "@abp/ng.theme.shared": "~10.6.0",
  "@abp/ng.core": "~10.6.0",
  "@ng-bootstrap/ng-bootstrap": "^21.0.0",
  "ng-zorro-antd": "^22.0.1"
}

5.2 ABP Theme Shared Internal Dependencies

@abp/ng.theme.shared v10.6.0 bundles its own @ng-bootstrap/ng-bootstrap v20.0.0.

5.3 Key Source Locations

  • abp-ng.theme.shared.mjs line 1775: contentChild('abpBody') signal query
  • abp-ng.theme.shared.mjs line 1826: toggle() spreads options() to ng-bootstrap
  • ng-bootstrap-ng-bootstrap-modal.mjs line 83: Backdrop style: 'z-index: 1055' hardcoded

5.4 Browser

Tested in Chrome 130+ and Edge 130+. Issue is CSS z-index stacking, not browser-specific.


6. Minimal Reproduction

6.1 Z-index Issue

Open a component via this.dialog.open(AlertComponent, { data, width: '80%' }). Inside that MatDialog component:

<abp-modal [(visible)]="openViewDocument">
  <ng-template #abpBody><p>Content here</p></ng-template>
</abp-modal>

Result: abp-modal renders behind the MatDialog overlay — invisible to the user.

6.2 contentChild Issue

<abp-modal [(visible)]="showModal">
  <ng-template *ngIf="isEditMode" #abpBody>
    <app-edit-form></app-edit-form>
  </ng-template>
  <ng-template *ngIf="!isEditMode" #abpBody>
    <app-view-only></app-view-only>
  </ng-template>
</abp-modal>

Result: Modal opens but body is empty — contentChild('abpBody') returns undefined.


7. Summary of Requests

| # | Request | Severity | |---|---------|----------| | 1 | Document the contentChild breaking change for *ngIf on <ng-template #abpBody> in migration guide | Critical | | 2 | Add z-index configuration to ModalComponent (e.g., zIndex input or CSS custom property) | High | | 3 | Document windowClass/backdropClass passthrough via [options] input | High | | 4 | Add runtime warning when abpBody() signal returns undefined but modal is visible | Medium | | 5 | Consider CDK overlay for modal rendering instead of ng-bootstrap to avoid z-index conflicts with other CDK-based components | Low (long-term) |


Reported by: TASConnect Platform Team Contact: Pradeep Pradyumna Attachments: Screenshots available from JIRA tickets VL-246XX and VL-246XX

I have shared details over email. Also I have enabled Debug. Post deployment, I will share the fresh logs

[maliming] said: ok : )

Sorry for the delayed response. After including changes as suggested, I still face the same issue.

Do let me know: apart from the identitymodel logs, is there anything else you would like me to share? I could do it over email. Also, let me know if we could connect over a short call I can walk you through the code and changes we have made so far. Thank you!

[maliming] said: TokenValidationParameters

thank you. Yaduraj is on a leave this week and the changes are not yet implemented. I just did and waiting for deployment. I'll update you soon. thank you!

Here are the logs from Identity and Gateway projects:

Identity API:

identitymodel-identity.txt

Gateway API:

identitymodel-gateway.txt

On the email, I'm sending you a copy of the Application and Network tab contents.

thanks!

Hi ABP team,

Is it possible that we could get over a short call, as we 're running short of time and we have critical deliveries dependent on this upgrade we did?

We're facing issues logging into the application post ABP IO upgrade. And I see some of your suggestions are helping but itsn;t fast enough for us to do it over support tickets and meet our deadlines.

Just sharing a summary of .NET and Angular upgrades we did here. UPGRADE_COMPLETION_REPORT.md

ANGULAR-22-ABP-10.6-UPGRADE-COMPLETE-SUMMARY.md

Pls review them and let us know when can we connect today? Thanks!

Angular 22 + ABP 10.6 + TypeScript 6.0 Upgrade Summary

Project: TASConnect Litmus Platform
Period: August 28 - September 1, 2026
PR: #3355
Branch: feature/R26.06_angular22-abp10-upgrade


Executive Summary

Successfully upgraded Angular 17.3.12 → 22.0.8 with ABP 8.3 → 10.6 and TypeScript 5.3 → 6.0 for backend .NET 10 compatibility.

Impact:

  • 740 files modified
  • ~738 components updated with standalone: false
  • 50+ DTOs fixed for TypeScript 6.0
  • 17 modules refactored for pipe/provider architecture

Status: ✅ Compilation: Success (0 errors)
⚠️ Warnings: Sass deprecations (non-blocking)
✅ Dev Server: Starts successfully
✅ Runtime: Application loads correctly


Version Changes

| Package | Before | After | |---------|--------|-------| | Angular | 17.3.12 | 22.0.8 | | TypeScript | 5.3.0 | 6.0.0 | | ABP Framework | 8.3.0 | 10.6.0 | | ng-zorro-antd | 17.4.1 | 22.0.1 | | Angular Material | 17.3.10 | 22.1.4 | | ng-bootstrap | 16.0.0 | 17.0.0 (downgraded from 18 for compatibility) |


Key Phases

Phase 1: Core Upgrade (Aug 28)

  • Upgraded Angular 17 → 22, TypeScript 5 → 6
  • Changed browserTarget → buildTarget in angular.json
  • Disabled strict mode temporarily for gradual migration

Phase 2: ABP Upgrade (Aug 28)

  • Upgraded all ABP packages to 10.6.0
  • Added LOGO_APP_NAME_TOKEN provider (required in ABP 10+)

Phase 3: TypeScript 6.0 Fixes (Aug 28)

  • Fixed TS2612 errors by adding declare keyword to 50+ DTOs
  • Example:
    export class MyDto extends PagedDto {
      declare sorting: string;  // ← Added 'declare'
    }
    

Phase 4: Component Architecture (Sep 1)

  • Added standalone: false to ~738 components
  • Fixed NG5002 two-way binding errors in 3 mat-select elements
  • Updated ngx-image-cropper usage (Module → Component)

Phase 5: Module Fixes (Aug 31 - Sep 1)

  • Broke circular dependency: SharedModule ⟷ CoreSharedModule
  • Removed DateFormatPipe from providers in 17 modules (pipes go in declarations, not providers)
  • Fixed AlphanumericAllowPasteDirective standalone flag

Phase 6: DatePipe Fix (Sep 1) ⭐ LATEST

  • Problem: Blank login page, NG0201 error: "No provider for DatePipe"
  • Cause: ABP's lazy-loaded AccountPublicModule needed DatePipe
  • Solution: Added DatePipe to global providers in app.module.ts

Breaking Changes

1. Component Standalone Declaration (HIGH)

Angular 22 defaults to standalone: true. All NgModule components need standalone: false.

@Component({
  standalone: false,  // ← Required
  selector: 'app-example',
  templateUrl: './example.component.html'
})

2. Two-Way Binding Restrictions (MEDIUM)

Complex expressions in [(value)] no longer supported.

<!-- ❌ Before -->
<mat-select [(value)]="form?.value.field">

<!-- ✅ After -->
<mat-select [formControl]="form?.controls['field']">

3. TypeScript 6.0 Property Redeclaration (HIGH)

Must use declare keyword for inherited properties.

4. Module Resolution (LOW)

Changed from node to bundler in tsconfig.json.

5. Angular.json Schema (LOW)

browserTarget renamed to buildTarget.

6. ABP Logo Configuration (MEDIUM)

Requires explicit LOGO_APP_NAME_TOKEN provider.

7. DatePipe Provider (HIGH) ⭐ NEW

Angular 22 requires DatePipe in global providers for lazy-loaded ABP modules.


Configuration Changes

tsconfig.json:

{
  "compilerOptions": {
    "target": "ES2022",
    "moduleResolution": "bundler",
    "strictPropertyInitialization": false,
    "useDefineForClassFields": false
  }
}

angular.json:

{
  "serve": {
    "options": {
      "buildTarget": "litmus:build"  // Changed from browserTarget
    }
  }
}

app.module.ts:

import { DatePipe } from '@angular/common';

@NgModule({
  providers: [
    DatePipe,  // ← Angular 22 fix for lazy-loaded modules
    // ...
  ]
})

Known Issues & Workarounds

1. ABP @angular/aria/tabs Polyfill ⚠️

Issue: ABP 10.6 imports non-existent @angular/aria/tabs.
Workaround: Create polyfill in node_modules/@angular/aria/tabs/.
Action: Recreate after every npm install.
Doc: See ABP-ANGULAR-22-POLYFILL-WORKAROUND.md

2. Sass Deprecation Warnings ⚠️

Issue: Sass @import will be removed in Dart Sass 3.0.
Impact: Non-blocking warnings.
Future: Migrate to @use and @forward syntax.

3. CommonJS Dependencies ⚠️

Affected: lodash, moment, highcharts, crypto-js, uuid.
Impact: Larger bundle size, no functional issues.

4. ng-bootstrap Version Constraint ✅

Fixed: Using v17 (v18 has afterRender issues).


Testing Requirements

Critical Priority

  • ✅ Login page (fixed with DatePipe)
  • ⬜ User authentication flow
  • ⬜ OAuth/OIDC
  • ⬜ Permission-based routing

High Priority

  • ⬜ File uploads (ABP 10.6 API changes)
  • ⬜ Reactive forms with mat-select
  • ⬜ NGXS state management
  • ⬜ Lazy-loaded modules DI

Medium Priority

  • ⬜ Dashboard/Charts (Highcharts)
  • ⬜ Modals/Dialogs (ng-bootstrap, Material)
  • ⬜ Data tables (ng-zorro)

Deployment Checklist

Pre-Deployment:

  • [ ] Integration tests pass
  • [ ] Browser compatibility verified
  • [ ] Performance acceptable
  • [ ] Code review complete

Build Configuration:

  • [ ] Set NODE_OPTIONS=--max-old-space-size=8192
  • [ ] Production build succeeds
  • [ ] Bundle sizes acceptable

ABP Polyfill:

  • [ ] Create node_modules/@angular/aria/tabs/ polyfill
  • [ ] Verify build with polyfill
  • [ ] Document for CI/CD

Post-Deployment:

  • [ ] Monitor errors (Sentry/CloudWatch)
  • [ ] Track authentication success rate
  • [ ] Watch for DI-related errors

Statistics

Code Changes:

  • 740 files modified
  • ~738 components updated
  • 50+ DTOs fixed
  • 17 modules refactored

Build Metrics:

  • Compilation: ~60s (was ~45s)
  • Node Memory: 8GB (was 4GB)
  • Errors: 0
  • Warnings: 45 (Sass deprecations)

Package Upgrades:

  • 47 total packages upgraded
  • 15 Angular core packages
  • 25 ABP Framework packages
  • 4 UI libraries
  • 3 build tools

Key Commits

  • 58b41a68 - Initial Angular 22 upgrade
  • 3ede8924 - ABP 10.6 upgrade
  • fda8ef48 - TypeScript 6.0 DTO fixes
  • 2ab9bcda - Complete upgrade with standalone:false
  • cdc6f407 - DatePipe provider fix ⭐
  • 377892a5 - DateFormatPipe provider fix (PR review)
  • 33b47d33 - Remove dead @HostListener code

Lessons Learned

What Worked:

  • Phased approach isolated issues
  • Temporarily disabling strict mode allowed gradual migration
  • Global DatePipe provider fixed lazy-loaded module DI issues

Challenges:

  • Angular 21 attempt failed (ABP requires 22.0.x)
  • TypeScript 6.0 required systematic DTO fixes
  • ABP @angular/aria/tabs needed workaround
  • ng-bootstrap v18 incompatible, downgraded to v17

Future:

  • Consider standalone component migration
  • Evaluate @angular/build (esbuild)
  • Monitor ABP for native Angular 22 support
  • Migrate Sass @import to @use/@forward

References

Documentation:

  • Angular 22: https://angular.dev/update-guide
  • TypeScript 6.0: https://devblogs.microsoft.com/typescript/announcing-typescript-6-0/
  • ABP 10.6: https://abp.io/docs/latest/release-info/migration-guides/abp-10-6

Internal Docs:

  • ABP-ANGULAR-22-POLYFILL-WORKAROUND.md
  • ANGULAR-22-ABP-10.6-FIX-SUMMARY.md

Contact: Pradeep.Pradyumna@tasconnect.com


Status: ✅ Complete
Last Updated: September 2, 2026

NO AI response please. Request you to go through the attached markdown files and respond

Showing 1 to 10 of 12 entries
Boost Your Development
ABP Live Training
Packages
See Trainings
Mastering ABP Framework Book
The Official Guide
Mastering
ABP Framework
Learn More
Mastering ABP Framework Book
Made with ❤️ on ABP v10.8.0-preview. Updated on November 16, 2026, 06:26
1
ABP Assistant
🔐 You need to be logged in to use the chatbot. Please log in first.