-
Notifications
You must be signed in to change notification settings - Fork 60
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
Angular 16 support to use standalone component and signals #101
Comments
Hi again @sheikalthaf ! Currently, there are no plans to update to Angular 16. That being said, if Angular 14 libraries are not compatible with Angular 17 (which is expected to be released soon), we may need to upgrade the Angular version to ensure the library's compatibility with Angular 17. |
Yes, then we can wait for Angular 17 update |
@llorenspujol, Angular 14 does not work with nodejs 18. If I need to upgrade to node 18 with angular 16 - will I still be able to depend on current angular-grid-layout version (angular14)? |
Hi, @llorenspujol |
@Jeredian Agreed, it is time to upgrade Angular Grid Layout to Angular 16 and export it as a standalone component. This way, full standalone apps can import AngularGridLayout. Having said that, even though Angular Grid Layout is currently written with Angular 14, it remains compatible with Angular 17, as far as you import it into an NgModule. In resume, I am open to PRs for upgrading to Angular 16 (not Angular 17), with Angular Grid Layout exported as a standalone component. You may want to take it @sheikalthaf |
@llorenspujol Did you have open the PRs ? |
Is anything planned regarding Angular 16 / 17 / 18? |
@llorenspujol Created the PR for v15 and v16 versions |
Do you have any plan to update to angular 16, so that we can make use of Standalone components and signals.
I'm ready to raise a PR for this
The text was updated successfully, but these errors were encountered: