spennyf
Results
2
comments of
spennyf
When I set my my prime ng in `package.json` from `"primeng": "^17.17.0",` to `"primeng": "17.2.0",` the issue is fixed. Looks like there is a bug i `17.17.0`
version `17.12.0` was the last working version `17.13.0` it does not work