Piotr Stępniewski
Piotr Stępniewski
@shajz `angular-eslint` is community driven package, thats why there could be some divergences. You can always create issue in their repository or even PR to align with latest recommendations.
@JeanMeche could this release also be synchronized with folks from `angular-eslint` as it's used by most projects using Angular?
Yeah we should be embracing web standards here.
@Akxe I think they just need to redo implementation of cdk overlay how it works and modals. Other stuff should be fine because it's uses cdk overlays.
Yes adding prefix `file:` helped
@vmasek is that big deal for you? Having `lodash-es` as peer dependency? It already ships with similar implementation, but for those who are using `lodash` it's beneficial to not bundle...
Please also add yourself as a contributor here are instructions https://allcontributors.org/docs/en/cli/usage#all-contributors-add
@vmasek I recommend using this feature from npm https://docs.npmjs.com/cli/v10/configuring-npm/package-json#overrides Personally I think replacing `lodash-es` for all library users is a bad idea. As it will increase their bundle sizes. However,...
@vmasek I will now close this PR and release a new slimmed-down version once Angular v18 is released. I would also extract config strict checks out of production and give...
@alan-agius4 @pkozlowski-opensource I'm an author of Angular Library and I want to have strict check on dev mode, but those should not end up in prod bundle. As you know...