-
-
Notifications
You must be signed in to change notification settings - Fork 26
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 11 compatibility #307
Comments
This is fixed in #314 |
This one too, @NathanWalker (sorry for the @mention spam) |
When will this be updated to for nativescript 8? @NathanWalker @agonper |
Hi @iameduardod, it should be working already with a minimal functionality if you install the schematics version 11.2.0-rc.0. You'll need Angular 11.2 and TypeScript ~4.1.0. Hope this helps. If you can try it out, please share with us if it works for you. |
So these steps to update to from a clean base? @agonper
|
@iameduardod I haven't tested with a shared project, but those dependency versions look good to me. Would be great to know if that still works. However, if you are starting a fresh code sharing project with NS8 the recommendation from the NS team is to use any of these options instead: https://docs.nativescript.org/code-sharing [email protected] are only guaranteed to work for NS NG component and module generation only. |
@agonper Thanks for sharing that link! Are those options going to replace nativescript-schematics? ETA for when nativescript-schematics will be sunset? |
Hi @iameduardod
For what the NS team says (source, slack community channel) that seems the plan, yes.
I cannot give you an answer to that question (I'm not part of the NS team, just helping them where I can). Perhaps @NathanWalker can give you an answer given he's in charge of the development of @nativescript/nx and @nstudio/xplat |
@agonper Thank you so much for the insights! |
Hi everyone.
Do you have any idea when the nativescript schematics will be updated to support angular 11??
thanks in advance
The text was updated successfully, but these errors were encountered: