fix(package): fixes #208 by compiling without Ivy - #209
Conversation
|
Warnings are found on analyzing the commit fee1501. 2 warnings: We recommend to address them as possible, for example, update outdated dependencies, fix the tool's configuration, configure If you are struggling with these errors or warnings, feel free to ask us via chat. 💬 |
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## master #209 +/- ##
=======================================
Coverage 98.75% 98.75%
=======================================
Files 7 7
Lines 161 161
Branches 47 47
=======================================
Hits 159 159
Misses 2 2 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
|
@bhuber2010 need help with these PR's, especially with ng-packagr is failing. once done aim is first to ng 10 and then eventually to ng11 and ng12 (supporting all intermediate versions) and finally we're showcasing it on fulls1z3/universal#755 |
** PR Type
What kind of change does this PR introduce?
** What is the current behavior?
Library can not be used in pre-Ivy projects
Issue Number: #208
** What is the new behavior?
Library works in pre-Ivy projects
** Does this PR introduce a breaking change?
** Other information
It's currently not recommended to build libraries with Ivy due to potentially losing support for ViewEngine compiled Angular projects.