Multiple Components v19 | ReferenceError: Cannot access 'Splitter' before initialization

[floreauwe]

Describe the bug

After upgrading primeNG from 19.0.6 to 19.0.7, I encounter this new error.

Test suite failed to run
ReferenceError: Cannot access 'Splitter' before initialization

Pull Request Link

No response

Reason for not contributing a PR

• Lack of time
• Unsure how to implement the fix/feature
• Difficulty understanding the codebase
• Other

Other Reason

No response

Reproducer

Environment

"dependencies": {
"@angular/animations": "^19.1.7",
"@angular/common": "^19.1.7",
"@angular/compiler": "^19.1.7",
"@angular/core": "^19.1.7",
"@angular/forms": "^19.1.7",
"@angular/platform-browser": "^19.1.7",
"@angular/platform-browser-dynamic": "^19.1.7",
"@angular/router": "^19.1.7",
"@ngx-translate/core": "^16.0.4",
"@primeng/themes": "^19.0.7",
"primeng": "^19.0.7",
"rxjs": "~7.8.0",
"tslib": "^2.8.1",
"zone.js": "~0.15.0"
},
"devDependencies": {
"@angular-devkit/build-angular": "^19.1.8",
"@angular/cli": "~19.1.8",
"@angular/compiler-cli": "^19.1.7",
"typescript": "^5.7.3"
},

Angular version

19.1.7

PrimeNG version

v19

Node version

22.12.0

Browser(s)

No response

Steps to reproduce the behavior

Upgrade from 19.0.6 to 19.0.7
Run spec file and test

Expected behavior

It should pass

[floreauwe]

Similar issue with old ones like 11931, 12945

[cthuemler]

I have the same issue with the Stepper Component using Jest, also after updating to 19.0.7:

ReferenceError: Cannot access 'Step' before initialization

[ratsey]

Adding a 'me too'.

  ● Test suite failed to run

    ReferenceError: Cannot access 'Splitter' before initialization

       5 | import { ContextMenuModule } from 'primeng/contextmenu';
       6 | import { SpeedDialModule } from 'primeng/speeddial';
    >  7 | import { SplitterModule } from 'primeng/splitter';
         | ^
       8 |
       9 | import { LayoutGuide } from '../../models/layout-guide';
      10 |

      at Object.<anonymous> (node_modules/primeng/fesm2022/primeng-splitter.mjs:138:264)

[DaSchTour]

What the heck is happening to this library? It feels like it falls apart more and more with every version 😟

[tsteuwer-accesso]

@floreauwe , can you change this to "Multiple Components" as this also affects Stepper as well.

[tsteuwer-accesso]

I put up a PR to fix this issue. The issue is PrimeNG is referencing classes that haven't been defined and you have to use forawrdRef. I made a PR but i don't know when the PrimeNG team looks at these.