-
Notifications
You must be signed in to change notification settings - Fork 17
feat(package): migrate to ng11 #137
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
updating deps and updating version in all projects BREAKING CHANGE: using ng11
ghost
commented
Apr 11, 2021
Sider detected 2 warnings on analyzing the commit 449ca26.
We recommend fixing them as possible by updating the dependencies, configuring the analysis tool, configuring sider.yml, turning off unused tools, and so on.
If you have problems or questions still, feel free to ask us via chat. 💬
You can turn off this notification if you don't want to receive it from now on.
@m7mdbadawy 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
updating deps and updating version in all projects
BREAKING CHANGE: using ng11
** PR Checklist
Please check if your PR fulfills the following requirements:
** PR Type
What kind of change does this PR introduce?
** What is the current behavior?
The current build uses angular 9
Issue Number: N/A
** What is the new behavior?
it should support angular 11
** Does this PR introduce a breaking change?
This uses angular 11 deps and compiler and should be used with angular 11
** Other information