You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
[x] bug report => Search github for a similar issue or PR before submitting
[ ] feature request => Please check if request is not on the roadmap already https://github.com/primefaces/primeng/wiki/Roadmap
[ ] support request => Please do not submit support request here, instead see http://forum.primefaces.org/viewforum.php?f=35
Plunkr Case (Bug Reports)
Please demonstrate your case at stackblitz by using the issue template below. Issues without a test case have much less possibility to be reviewd in detail and assisted.
Current behavior
When upgrading from 11.2.3 to 11.3.0
Package "primeng" has an incompatible peer dependency to "zone.js" (requires "^0.10.2", would install "0.11.4")
Expected behavior
Given that (at least from our usage) there is no issue with current usage of PrimeNG's Tree features in an app using zone.js 0.11.4, no warning about peer dependencies
Minimal reproduction of the problem with instructions
Starting place: primeng@11.2.3, zone.js@0.11.4
ng update primeng karma @types/node @types/jasmine
See output as mentioned above.
What is the motivation / use case for changing the behavior?
Please tell us about your environment:
Angular version: 11
PrimeNG version: 11
Browser: [all | Chrome XX | Firefox XX | IE XX | Safari XX | Mobile Chrome XX | Android X.X Web Browser | iOS XX Safari | iOS XX UIWebView | iOS XX WKWebView ]
Language: [all | TypeScript X.X | ES6/7 | ES5]
Node (for AoT issues):node --version = 14.5.3
The text was updated successfully, but these errors were encountered:
yigitfindikli
added
the
Type: Bug
Issue contains a bug related to a specific component. Something about the component is not working
label
Mar 11, 2021
I'm submitting a ... (check one with "x")
Plunkr Case (Bug Reports)
Please demonstrate your case at stackblitz by using the issue template below. Issues without a test case have much less possibility to be reviewd in detail and assisted.
https://stackblitz.com/github/primefaces/primeng-issue-template
Current behavior
When upgrading from 11.2.3 to 11.3.0
Expected behavior
Given that (at least from our usage) there is no issue with current usage of PrimeNG's Tree features in an app using zone.js 0.11.4, no warning about peer dependencies
Minimal reproduction of the problem with instructions
ng update primeng karma @types/node @types/jasmine
What is the motivation / use case for changing the behavior?
Please tell us about your environment:
Language: [all | TypeScript X.X | ES6/7 | ES5]
Node (for AoT issues):
node --version
= 14.5.3The text was updated successfully, but these errors were encountered: