Closed ghmj2417 closed 3 years ago
This is the consequence of an error I made in #356 , I have however proposed #360 to fix the issue. I see it just got merged seconds ago, that should fix the problem without the need for a major version bump ;)
fixed in 7.3.1
@Timebutt Works for me. Thank you for fixing it.
This issue does not occur in 7.2.0. I am using Angular 12.1
It looks like going from 7.2 to 7.3 introduces some breaking changes when using angular 12. Might be better to move 7.3.0 to 8.0.0 so users using ^7.x.x don't encounter this issue.