`Angular 19` Support #16827

mertsincan · 2024-11-22T16:01:55Z

Details; #16783

AStoker · 2024-11-22T16:19:00Z

If it helps, here's a list of files that needed to be updated in my testing. The Docs still have a lot of work though. AStoker@a1bad87

NateRadebaugh · 2024-11-25T11:33:19Z

Can this be back-ported to a 17.x release once this is ready?

mertsincan · 2024-11-25T13:47:17Z

Today, we had a detailed meeting about Angular 19 and decided to support it with PrimeNG 19. We are very close to the PrimeNG 18.Final. After releasing it, we plan to release PrimeNG 19.rc.1 within 1 to 2 weeks. Thanks a lot for your understanding!

mertsincan · 2024-11-25T13:50:26Z

Can this be back-ported to a 17.x release once this is ready?

Unfortunately, we do not plan to port it to version 17. Primeng versions will be released following the Angular versions. Otherwise, there will be many breakages in frameworks and libraries that are under such active development. I think this is the most logical thing.

yarikwest · 2024-12-10T11:55:27Z

Hi everyone,

Thank you so much for the PRs and feedback! PrimeNG 19 now works with Angular 19. Today, we plan to release PrimeNG 19-rc.1 so you can test it and share your thoughts. master...v19

I’d also like to talk about what’s next for PrimeNG 20. In v18 and v19, our main focus was building the new theming engine, and now it’s complete. For PrimeNG 20, we want to improve the codebase completely. This includes using strict types, adding more tests, moving to a signal-based and zoneless structure, and updating all components with the latest best Angular practices. We have a lot of internal improvements planned and will share more details with you soon.

When is the planned final release of v19?

mertsincan · 2024-12-10T11:59:19Z

When is the planned final release of v19?

Unless there are any major issues, we plan to release PrimeNG v19.Final the next week.

slawanextlevels · 2024-12-10T12:16:19Z

I got master...v19 running. Thank you

mertsincan · 2024-12-10T13:35:37Z

PrimeNG 19.0.0-rc.1 Released; https://www.npmjs.com/package/primeng/v/19.0.0-rc.1

dalenguyen · 2024-12-10T14:31:40Z

Confirmed that 19.0.0-rc.1 fixed the Uncaught TypeError: fn is not a function issue on my end :)

gbarrionuevo · 2024-12-10T23:29:14Z

#17005

dragsense · 2024-12-11T18:29:08Z

PrimeNG 19.0.0-rc.1 working fine with angular 19

alvaroaxo · 2024-12-12T02:33:28Z

Confirmed, PrimeNG 19rc works with Angular 19

lalo-mx · 2024-12-13T15:09:51Z

I have an issue with 19rc, how are the styles configured now?

@import "primeng/resources/themes/fluent-light/theme.css";

X [ERROR] Could not resolve "primeng/resources/themes/fluent-light/theme.css"

    src/primeng.scss:1:8:
      1 │ @import "primeng/resources/themes/fluent-light/theme.css";
        ╵         ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

  The path "./resources/themes/fluent-light/theme.css" is not exported by package "primeng":

    node_modules/primeng/package.json:46:13:
      46 │   "exports": {
         ╵              ^

Delagen · 2024-12-13T17:33:24Z

@lalo-mx RTFM, migration guide is published https://primeng.org/guides/migration

dragsense · 2024-12-13T17:49:19Z

I have an issue with 19rc, how are the styles configured now?

@import "primeng/resources/themes/fluent-light/theme.css";

X [ERROR] Could not resolve "primeng/resources/themes/fluent-light/theme.css"

    src/primeng.scss:1:8:
      1 │ @import "primeng/resources/themes/fluent-light/theme.css";
        ╵         ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

  The path "./resources/themes/fluent-light/theme.css" is not exported by package "primeng":

    node_modules/primeng/package.json:46:13:
      46 │   "exports": {
         ╵              ^

no need to import the css files.

https://primeng.org/theming

Configuration API
Theme
The theme property is used to customize the initial theme.

import { ApplicationConfig } from '@angular/core';
import { provideAnimationsAsync } from '@angular/platform-browser/animations/async';
import { providePrimeNG } from 'primeng/config';
import Aura from '@primeng/themes/aura';

export const appConfig: ApplicationConfig = {
providers: [
provideAnimationsAsync(),
providePrimeNG({
theme: {
preset: Aura
}
})
]
};

ThoSap · 2024-12-30T11:25:17Z

@radarsu I do the same, I have a PrimeNG 17.18.15 application with Angular 19.0.5 and it is completely zoneless with ChangeDetectionStrategy.OnPush and signals.

Zoneless with signals everywhere already worked before I upgraded to Angular 19 with Angular 18.2.0 and PrimeNG 17.18.9, no issues have been reported by any user so far and Zoneless with this setup has been in production since May 2024.

@JakeAi yeah, the signals make whole codebase so much more managable. I'd recommend mastering them quickly and Angular 19 release is crazy good, so on new project you might want to consider upgrading quickly.

I do a project with Angular 19 fully based on signals, primeng 18 and tailwind v4 beta. Figuring out perfect setup was tough, but those new releases solve so many problems I was struggling with in the past it's worth it (state management with signals feels so much better, management of primitive and semantic CSS values and components, theming and light/dark modes).

I even uninstalled zone.js and did zoneless angular and everything is working great, I no longer have obscured stack traces.

Feel free to contact me privately if you'd like to copy my setup.

@imaksp Haven't yet encountered any problems without it. I use OnPush changeDetection strategy and manage data via signals everywhere. But so far I use just few simple components from PrimeNG in that setup, maybe some advanced ones will have problems.

sergey-morenets · 2025-01-05T11:30:47Z

@lalo-mx RTFM, migration guide is published https://primeng.org/guides/migration

Hi @Delagen

It's not clear whether Primeng 19+ supports non-standalone configuration. In the "Getting started" guide(https://primeng.org/installation) there's a following configuration which can be applied for standalone components only:

export const appConfig: ApplicationConfig = {
    providers: [
        provideAnimationsAsync(),
        providePrimeNG({
            theme: {
                preset: Aura
            }
        })
    ]
};

Delagen · 2025-01-05T12:56:49Z

@sergey-morenets It's common configuration whenever use standalone or not. It's just new syntax and provider functions. Just read docs.

ibandim123 · 2025-02-20T15:34:10Z

Confirmed, PrimeNG 19rc works with Angular 19

This is confirmed?

jex-novatec · 2025-02-20T16:14:39Z

For me it's not working with the following versions:
"dependencies": { "@angular/common": "~19.1.0", "@angular/compiler": "~19.1.0", "@angular/core": "~19.1.0", "@primeng/themes": "^19.0.6", "primeng": "^19.0.5" },

gatzsche · 2025-02-20T16:32:38Z

For me it's not working with the following versions: "dependencies": { "@angular/common": "~19.1.0", "@angular/compiler": "~19.1.0", "@angular/core": "~19.1.0", "@primeng/themes": "^19.0.6", "primeng": "^19.0.5" },

Are there versions that are working?

samjs89 · 2025-02-20T17:15:18Z

@jex-novatec Same for me. not working. below are my dependencies.

{ "@angular/animations": "^19.1.0", "@angular/common": "^19.1.0", "@angular/compiler": "^19.1.0", "@angular/core": "^19.1.0", "@angular/forms": "^19.1.0", "@angular/platform-browser": "^19.1.0", "@angular/platform-browser-dynamic": "^19.1.0", "@angular/router": "^19.1.0", "rxjs": "~7.8.0", "tslib": "^2.3.0", "zone.js": "~0.15.0", "@primeng/themes": "^19.0.6", "primeng": "^19.0.6" }

gatzsche · 2025-02-20T17:44:03Z

The error results from primeng-icons-baseicon.mjs:

features: [i0.ɵɵProvidersFeature([BaseIconStyle]), i0.ɵɵInputTransformsFeature, i0.ɵɵInheritDefinitionFeature],

The value i0.ɵɵInputTransformsFeature is undefined.

i0 again is imported via import * as i0 from '@angular/core';

Why is i0.eeInputTransformFeature undefined?

gatzsche · 2025-02-20T17:55:07Z

I found it: ɵɵInputTransformsFeature has been removed in Angular 19.1.7. It is available in Angular 19.1.6.

Restricting Angular to 19.1.6 should remove the issue temporarily.

danielschmitz · 2025-02-20T18:07:23Z

still not working for me.

PS: i do the postInstall

"dependencies": {
    "@angular/animations": "^19.1.0",
    "@angular/common": "^19.1.0",
    "@angular/compiler": "^19.1.0",
    "@angular/core": "^19.1.0",
    "@angular/forms": "^19.1.0",
    "@angular/platform-browser": "^19.1.0",
    "@angular/platform-browser-dynamic": "^19.1.0",
    "@angular/router": "^19.1.0",
    "@primeng/themes": "^19.0.6",
    "primeng": "^19.0.6",
    "rxjs": "~7.8.0",
    "tslib": "^2.3.0",
    "zone.js": "~0.15.0"
  },
  "devDependencies": {
    "@angular-devkit/build-angular": "^19.1.5",
    "@angular/cli": "^19.1.5",
    "@angular/compiler-cli": "^19.1.0",
    "@types/jasmine": "~5.1.0",
    "jasmine-core": "~5.5.0",
    "karma": "~6.4.0",
    "karma-chrome-launcher": "~3.2.0",
    "karma-coverage": "~2.2.0",
    "karma-jasmine": "~5.1.0",
    "karma-jasmine-html-reporter": "~2.1.0",
    "typescript": "~5.7.2"
  }

gatzsche · 2025-02-20T18:09:45Z

You need to remove the ^ from the version numbers, which means that in the background minor patches like 19.1.7 are installed. But then you need to increase the versions manually.

danielschmitz · 2025-02-20T18:26:59Z

You need to remove the ^ from the version numbers, which means that in the background minor patches like 19.1.7 are installed. But then you need to increase the versions manually.

"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",
    "@primeng/themes": "^19.0.6",
    "primeng": "^19.0.6",
    "rxjs": "~7.8.0",
    "tslib": "^2.3.0",
    "zone.js": "~0.15.0"
  },
  "devDependencies": {
    "@angular-devkit/build-angular": "^19.1.5",
    "@angular/cli": "^19.1.5",
    "@angular/compiler-cli": "19.1.7",
    "@types/jasmine": "~5.1.0",
    "jasmine-core": "~5.5.0",
    "karma": "~6.4.0",
    "karma-chrome-launcher": "~3.2.0",
    "karma-coverage": "~2.2.0",
    "karma-jasmine": "~5.1.0",
    "karma-jasmine-html-reporter": "~2.1.0",
    "typescript": "~5.7.2"
  }

still not working... any tip?

gatzsche · 2025-02-20T18:27:06Z

This should do it:

"dependencies": {
    "@angular/animations": "<=19.1.6",
    "@angular/common": "<=19.1.6",
    "@angular/compiler": "<=19.1.6",
    "@angular/core": "<=19.1.6",
    "@angular/forms": "<=19.1.6",
    "@angular/platform-browser": "<=19.1.6",
    "@angular/platform-browser-dynamic": "<=19.1.6",
    "@angular/router": "<=19.1.6",
    "@primeng/themes": "^19.0.6",
    "primeng": "^19.0.6",
    "rxjs": "~7.8.0",
    "tslib": "^2.3.0",
    "zone.js": "~0.15.0"
  },
  "devDependencies": {
    "@angular-devkit/build-angular": "<=19.1.5",
    "@angular/cli": "<=19.1.6",
    "@angular/compiler-cli": "<=19.1.6",
    "@types/jasmine": "~5.1.0",
    "jasmine-core": "~5.5.0",
    "karma": "~6.4.0",
    "karma-chrome-launcher": "~3.2.0",
    "karma-coverage": "~2.2.0",
    "karma-jasmine": "~5.1.0",
    "karma-jasmine-html-reporter": "~2.1.0",
    "typescript": "~5.7.2"
  }

gatzsche · 2025-02-20T18:33:13Z

still not working... any tip?

See my comment before. Version 19.1.7 is broken. Replace it by <= 19.1.6.

danielschmitz · 2025-02-20T18:36:18Z

It didn't work either. Can you publish a newly created project on GitHub with only the button from the tutorial working?

In theory, PrimeNG should work just by doing the standard installation, without this postinstall or version adjustment. I hope they fix this ASAP.

gatzsche · 2025-02-20T18:38:28Z

There is already an issue for that:

#17730

pastagaz69 · 2025-02-21T17:46:20Z

still not working... any tip?

See my comment before. Version 19.1.7 is broken. Replace it by <= 19.1.6.

Thanks a lot ! workaround works like a charm

mertsincan pinned this issue Nov 22, 2024

mertsincan assigned mertsincan and cetincakiroglu Nov 22, 2024

mertsincan added the Status: Pending Review Issue or pull request is being reviewed by Core Team label Nov 22, 2024

mertsincan added this to the 18.0.0-rc.2 milestone Nov 22, 2024

mertsincan added this to PrimeNG Nov 22, 2024

mertsincan moved this to Review in PrimeNG Nov 22, 2024

github-actions bot added the Status: Needs Triage Issue will be reviewed by Core Team and a relevant label will be added as soon as possible label Nov 22, 2024

mertsincan linked a pull request Nov 22, 2024 that will close this issue

feat(angular): allow/support Angular 19 with zone.js 0.15 #16783

Merged

This was referenced Nov 22, 2024

Vite - TypeError: fn is not a function #16813

Closed

feat(angular): allow/support Angular 19 with zone.js 0.15 #16783

Merged

mertsincan removed the Status: Needs Triage Issue will be reviewed by Core Team and a relevant label will be added as soon as possible label Nov 22, 2024

thielpa mentioned this issue Nov 25, 2024

chore(deps): Update primeng to v19.0.1 ls1intum/Helios#52

Merged

mertsincan added a commit that referenced this issue Nov 25, 2024

Refactor #16827

3bd2499

mertsincan closed this as completed in #16783 Nov 25, 2024

github-project-automation bot moved this from Review to Done in PrimeNG Nov 25, 2024

mertsincan removed a link to a pull request Nov 25, 2024

feat(angular): allow/support Angular 19 with zone.js 0.15 #16783

Merged

mertsincan reopened this Nov 25, 2024

mertsincan moved this from Done to In Progress in PrimeNG Nov 25, 2024

github-actions bot added the Status: Needs Triage Issue will be reviewed by Core Team and a relevant label will be added as soon as possible label Nov 25, 2024

mertsincan modified the milestones: 18.0.0-rc.2, 19.x Nov 25, 2024

mertsincan removed this from PrimeNG Nov 25, 2024

KeithGillette mentioned this issue Dec 15, 2024

Error on unit test angular 19 #17057

Closed

shaman-apprentice mentioned this issue Jan 21, 2025

Component: SelectionTree, Bug when selecting something while having filtered value #16792

Open

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

`Angular 19` Support #16827

`Angular 19` Support #16827

mertsincan commented Nov 22, 2024

AStoker commented Nov 22, 2024

NateRadebaugh commented Nov 25, 2024

mertsincan commented Nov 25, 2024

mertsincan commented Nov 25, 2024

yarikwest commented Dec 10, 2024

mertsincan commented Dec 10, 2024 •

edited

Loading

slawanextlevels commented Dec 10, 2024

mertsincan commented Dec 10, 2024

dalenguyen commented Dec 10, 2024

gbarrionuevo commented Dec 10, 2024

dragsense commented Dec 11, 2024

alvaroaxo commented Dec 12, 2024

lalo-mx commented Dec 13, 2024

Delagen commented Dec 13, 2024

dragsense commented Dec 13, 2024

ThoSap commented Dec 30, 2024

sergey-morenets commented Jan 5, 2025

Delagen commented Jan 5, 2025

ibandim123 commented Feb 20, 2025 •

edited

Loading

jex-novatec commented Feb 20, 2025

gatzsche commented Feb 20, 2025

samjs89 commented Feb 20, 2025 •

edited

Loading

gatzsche commented Feb 20, 2025 •

edited

Loading

gatzsche commented Feb 20, 2025

danielschmitz commented Feb 20, 2025

gatzsche commented Feb 20, 2025

danielschmitz commented Feb 20, 2025

gatzsche commented Feb 20, 2025

gatzsche commented Feb 20, 2025

danielschmitz commented Feb 20, 2025

gatzsche commented Feb 20, 2025

pastagaz69 commented Feb 21, 2025

Angular 19 Support #16827

Angular 19 Support #16827

Comments

mertsincan commented Nov 22, 2024

AStoker commented Nov 22, 2024

NateRadebaugh commented Nov 25, 2024

mertsincan commented Nov 25, 2024

mertsincan commented Nov 25, 2024

yarikwest commented Dec 10, 2024

mertsincan commented Dec 10, 2024 • edited Loading

slawanextlevels commented Dec 10, 2024

mertsincan commented Dec 10, 2024

dalenguyen commented Dec 10, 2024

gbarrionuevo commented Dec 10, 2024

dragsense commented Dec 11, 2024

alvaroaxo commented Dec 12, 2024

lalo-mx commented Dec 13, 2024

Delagen commented Dec 13, 2024

dragsense commented Dec 13, 2024

ThoSap commented Dec 30, 2024

sergey-morenets commented Jan 5, 2025

Delagen commented Jan 5, 2025

ibandim123 commented Feb 20, 2025 • edited Loading

jex-novatec commented Feb 20, 2025

gatzsche commented Feb 20, 2025

samjs89 commented Feb 20, 2025 • edited Loading

gatzsche commented Feb 20, 2025 • edited Loading

gatzsche commented Feb 20, 2025

danielschmitz commented Feb 20, 2025

gatzsche commented Feb 20, 2025

danielschmitz commented Feb 20, 2025

gatzsche commented Feb 20, 2025

gatzsche commented Feb 20, 2025

danielschmitz commented Feb 20, 2025

gatzsche commented Feb 20, 2025

pastagaz69 commented Feb 21, 2025

`Angular 19` Support #16827

`Angular 19` Support #16827

mertsincan commented Dec 10, 2024 •

edited

Loading

ibandim123 commented Feb 20, 2025 •

edited

Loading

samjs89 commented Feb 20, 2025 •

edited

Loading

gatzsche commented Feb 20, 2025 •

edited

Loading