I think its because the ivy-built library wouldn't be able to be used with angular 8 (view-engine) projects, they probably want library maintainers to be compatible with older versions.
But once you published your library, and use in in your Ivy app, you'll still receive the benefits, cause its all optimized in the end.
Let me try to understand. I think you are saying that for all of the developers out there still in Angular 8, these parts would not mesh. It's an environment issue with the development environment.
In other languages like C# one cannot import libraries higher than the current project, but the warnings are clear, it just cannot be done. Maybe the whole import system doesn't take a release into account?
One thing is clear to me, the NPM Module environment is a mess for sure.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
I think its because the ivy-built library wouldn't be able to be used with angular 8 (view-engine) projects, they probably want library maintainers to be compatible with older versions.
But once you published your library, and use in in your Ivy app, you'll still receive the benefits, cause its all optimized in the end.
Let me try to understand. I think you are saying that for all of the developers out there still in Angular 8, these parts would not mesh. It's an environment issue with the development environment.
In other languages like C# one cannot import libraries higher than the current project, but the warnings are clear, it just cannot be done. Maybe the whole import system doesn't take a release into account?
One thing is clear to me, the NPM Module environment is a mess for sure.