-
-
Notifications
You must be signed in to change notification settings - Fork 241
Angular 9 #2060
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
Comments
Hi @simkepal , Thank you for the interest of Angular 9 and its integration in NativeScript. We have been working closely with the Angular team in order to make sure that the Ivy feature of the Angular 9.0.0 release will be available in NativeScript with as little requirements as possible. While the story about Ivy is still not fully functioning in NativeScript we have resolved all other changes and compatibility requirement that come with Angular 9.0.0. You can test an early version of the As already mentioned the Ivy functionality is still in development and is currently not working so you will have to disable it. After installing the
Note that this is an very early "preview" of the nativescript-angular package integration with Angular 9.0.0, if you notice any issue please report them here. |
Hi, thanks for your work. Could you tell me when Angular 9 support for Nativescript is expected? Angular 9 has been officially released. |
I am also looking forward to Angular 9. Especially components such as the google maps component will be great too use: https://github.com/angular/components/tree/master/src/google-maps |
To me the most exciting thing about Angular 9 is it supports TypeScript 3.7, with optional chaining. Looking forward to cleaning up a bunch of code as soon as this is ready. 😀 |
Crap upgraded angular on a large project with a web site and an app and the Nativescript side is broken. Any ideas on when NativeScript will work again? |
Ok cool after actually RTFM I can confirm it is working with the following steps: npm i nativescript-angular@ivy
./node_modules/.bin/update-app-ng-deps
npm i |
Unfortunately my application doesn't work after migration to Angular 9. The web application works well, but in ns app I have a lot of bugs during the launch. I tried to create new empty code-sharing project and then migrating to ng 9 with the same results :(. Finally I can't migrate my web app to ng 9 because of that. |
I've tried to upgrade Nativescript Hello world application to angular 9 with nativescript-angular@ivy but I've ended with error
Does anybody know what might be the problem? |
@vinckobb @Arystosedes @BenSjoberg @samirotiv @Firetrip Give this a shot: |
@NathanWalker I've tried your PR but still same error. Created repo with your version of nativescript angular so you can try https://github.com/vinckobb/nativescript-angular-demo |
Thanks @vinckobb that's super helpful! I'll give it shot and see if some subtle project setup issue may be getting in way with what you got there. I'll have chance to take peek on Wednesday. |
@vinckobb here ya go: vinckobb/nativescript-angular-demo#1 |
@NathanWalker tried your PR but still same error while compiling with ngcc. I'm using Windows right now so it can be Windows related. I'll try os x in the evening. So it definitely looks like Windows related problem. It works like a charm on OS X. I'm going check what might be the problem. Thanks a lot @NathanWalker |
@vinckobb my guess is likely Windows has issue with the postinstall handling and/or ngcc trying to compile node_modules and runs into path/directory issue possibly. Lemme know if you find what is affecting Windows. Thanks for letting us know Mac/OS X worked for you 👍 |
@NathanWalker I had to explicitly list exported names in form/value-accessor to make it work on Windows as you can see in vinckobb@4eb895f Don't know why I had to do this for this particular index.ts because http-client works without any problems. |
@vinckobb did you compile your own version of |
@joshcomley yes I did. I've updated my repo https://github.com/vinckobb/nativescript-angular-demo with compiled version of You can compile it yourself if you want. Clone or fork |
@joshcomley @vinckobb for ease I posted the compiled working v9 versions to a repo - these include the fix to exports for windows as well, just set your
Then reference the notes made here regarding tsconfig and other details for Ivy compliance: |
@vinckobb i pushed another fix to that PR that may have also been affecting forms and similar to what you had mentioned on windows. With this final adjustment I’m seeing stable Ivy behavior: The latest remote tgz’s provided here have all latest fixes:
|
@NathanWalker any update to support angular v9? |
Any Update to this? |
All details to use Angular 9 with NativeScript today can be found here: #2124 (comment) If anyone encounters issue with instructions provided, please post a public repo here and what you are running into and would be happy to help. |
@NathanWalker Thanks for the quick comment!!! I'll give it a shot. |
An alternative is switching to a framework that already supports v9 https://twitter.com/LiamDeBeasi/status/1261298258506375169 |
Hi Guys, I am wondering if the Angular+NativeScript is still in development. I am new to Angular and I liked it a lot, so would be greate if we could use Angular with NativeScript. |
Hi @handelcamilo thanks for the comment - the Angular 9 Ivy support in #2124 will be merged and published by no later than Wednesday next week along with some long awaited goodies like true async APP_INITIALIZER support and some nice support for easy animated launch screens given async launch conditions 👍 |
Good to know @NathanWalker!! I was afraid because the last change on this project was in February.. This is a very and important project to simply die hheeheh and you are doing a great job! I hope I can help with any time soon. Thanks. |
@NathanWalker is the next release going to support the angular 9 i18n system? |
@hrueger I haven't tried their i18n commands yet and the configuration specified in that doc but definitely seems like we could make that work (if it doesn't already). I have often used ngx-translate for all i18n on {N} apps as it's a very solid solution but I definitely think the i18n solution the angular team specifies should be able to work. |
$localize seems not to be working. I also cannot find anything regarding nativescript and $localize (or Angular 9 in general). When can we expect a solution as this is really blocking us from migrating our app to NativeScript? |
Why is the |
They are the same package. You can switch to @nativescript/angular |
@hrueger - @dimitri-bret is correct -
|
@NathanWalker Thanks, unfortunately I still have issue #2171 so I can't confirm that it's working. |
Hello,
I have a question: Is there already something to test out NativeScript with Angular 9? I am building an app for web, which will go out in December and thinking about to have also mobile app.
Thanks for answer!
The text was updated successfully, but these errors were encountered: