You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently there is no support for 4.0, see #1. At the moment, Angular is on 4.0.0-RC.1 and 4.0.0 final is scheduled to officially release on 2017-03-22. Unfortunately, building ng-block-ui for 4.x is not backwards compatible with 2.x.
Proposal
Since the official release is a few weeks off and it will take a while for everyone to upgrade to 4.0. I think it would be best if a next tag was created in npm (this is what the angular team currently uses for future releases). I will be starting at 1.0.0-beta.0 and support 4.x. Any features/fixes added to the current version (0.3.0) will be added into this version. Once I feel like Angular 4.0 is being widely adopted I will point the npm latest tag to 1.0.0 so that will be the default when installing from npm.
The text was updated successfully, but these errors were encountered:
Issue
Currently there is no support for 4.0, see #1. At the moment, Angular is on 4.0.0-RC.1 and 4.0.0 final is scheduled to officially release on 2017-03-22. Unfortunately, building ng-block-ui for 4.x is not backwards compatible with 2.x.
Proposal
Since the official release is a few weeks off and it will take a while for everyone to upgrade to 4.0. I think it would be best if a
next
tag was created in npm (this is what the angular team currently uses for future releases). I will be starting at 1.0.0-beta.0 and support 4.x. Any features/fixes added to the current version (0.3.0) will be added into this version. Once I feel like Angular 4.0 is being widely adopted I will point the npmlatest
tag to 1.0.0 so that will be the default when installing from npm.The text was updated successfully, but these errors were encountered: