Frankitch

Hi @JanMalch Are you still working on this? Is it safe to use in production? This plugin adresses perfectly my needs and matches existing features on Akita or NGRX. This...

Hi, same issue for me, any news on that one @leosvelperez ?

I also have no error with `yarn` when I run it locally but I cannot afford to switch my whole workflow to `yarn`.

I've found a [solution for npm](https://github.com/nrwl/nx/discussions/10692#discussioncomment-3507611)

Same problem here but also while serving angular.

This issue is still present in angular material v15 (MDC). It can be checked on angular material docs: https://material.angular.io/components/input/overview But wierdly, this does not happen on all inputs in docs...

Same issue for me, my workaround: ``` .mat-mdc-unelevated-button.mat-primary { --mdc-filled-button-label-text-color: var(--player-primary-contrast-500); } .mat-mdc-unelevated-button.mat-accent { --mdc-filled-button-label-text-color: var(--player-accent-contrast-500); } .mat-mdc-raised-button.mat-primary { --mdc-protected-button-label-text-color: var(--player-primary-contrast-500); } .mat-mdc-raised-button.mat-accent { --mdc-protected-button-label-text-color: var(--player-accent-contrast-500); } ```

@jchristensen726 I am facing the same issue but I have noticed that if the form field appearance is set to `outline` instead of `fill` (the default one), it works. I...