-
Notifications
You must be signed in to change notification settings - Fork 6
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
Startup time #9
Comments
Hey, @Dutchboy, Are you trying to run the samples with webpack or without it? |
Heyyyy @sis0k0 Stanimira!! You too answered so quickly!!! (It's "labour day" today, meaning no-work in most places) So, you are convinced - together with your colleague @NickIliev I will (somehow) get my future app booting up in 4 to 2.5 seconds?... That assures me enough to continue my road to develop... With regards to your question, I've just copied your LazyNinjas repo and clean-install-build (release) it as-is, which gave me a start time of these 10-13 seconds... From my own side, there is still a lot to do to get my whole application finished, so no stress here, before end of May... I do hope I can "harass" you (both) if I can't get it to load in 2.5 to 4 seconds, including source code, if necessary :-) Thanks!!!!!!!! Lars |
Yup, you can try to build it with webpack with the following steps:
|
First, again, I'm amazed how quick your response was / is.... I already tried it yesterday evening, with a clone I already had of your repo, but that showed some errors - I left it there, to repeat it today... A clean clone, checkout, npm i But this time too has some errors.... First error I knew it had to do with an older version of nativescript-dev-webpack, so I forced it to version 0.4.1 (the one you yesterday committed :-) ) Then, the same errors came up as yesterday evening... WARNING in ../~/tns-core-modules/ui/frame/frame.android.js
I'm currently doing this on my Win10, but if you want I, I could reproduce it on a mac or ubuntu too... Any thoughts?? |
This is a Windows issue with paths casing. This comment should fix it for you: PatrickJS/PatrickJS-starter#926 (comment) |
Hi!! Of course, first I went to look the link you gave me... But then I realized I could give it a try at my macOS Sierra machine.... I did the clone/checkout/npm i/npm run There, it does go further, installing it on a virtual machine, and then it crashed too
So, now I'm going to my Ubuntu machine... Hold on... Hmmm.... same problems.... I am so sorry, but do you have any suggestions?.... |
I'll check it tomorrow. Meanwhile, can you share the error log from your device? |
Hi Stanimira! Thanks again for answering so quickly! I'm almost humbled... Okay... About the errorlog of my device... It is still on a Genymotion emulator... I only got to copy the first lines of the stacktrace, but it's obvious because the nativescript-dev-webpack didn't get it right compiling the bundles... I think....
Looks ugly... The errors (initially warnings, then further-on errors) while Okay, first.... the whole output.... (I hate long listings! You asked for it :-) )
Any hints? The thing is, I got another repo working, even though that one is still slow, with the 13 seconds startup |
Hi @sis0k0 Stanimira! I've just upgraded to 3.0.0 and did a fresh install (--ng), nativescript-dev-webpack run npm start-android-bundle --aot --uglify So, that IS an improvement! At first, I did the above without ng, thus plain js... So, we're getting there... (still a problem with the css loader) |
Hey there, I updated the app to 3.0.0. We've tested this with Nexus 5 - android 5.0 API lvl 21 (~3.1 sec first run, ~2.9 sec second) and LG Mini 2 - android API lvl 19 (~3.5 sec first run, ~3.2 sec second). |
@sis0k0 yes I will - as soon as I'm at my desk! Mean while, can you tell me how you got the timing so accurate? Do you use a monitoring app for that? |
|
@sis0k0 Hi!... I've checkout to aot - correct? The first start-android-bundle successfully built and installed and then crashed (and burnt) on my android device itself... Honor 5X (from Huawei) Then, when I rebuilt again, I got the same messages as above, one of them:
What I did see is that in the package.json the When I compared the package.json between your webpack-sass repo and the ninjas/aot I saw some other diffs.... |
I think it's the same windows-related issue with casing. Can you clone the repo in a dir with all lowercase name?
|
@sis0k0 I did it again :-) no, same warnings, now I'm trying it at my mac |
git checkout aot - right? |
no.... also on the Mac - warnings |
but the webpack-sass works fine |
What are the warnings? |
@sis0k0 oh, same as the above.... |
Ok, can you try to manually rename the app dir? |
Sorry for answering so late!!!!!! I did a clean When processing, it shows the same warnings as before.
Then, on the phone it errors... The adb logcat | grep Displayed shows:
And oh, Nathan Walker has it working on his advanced seed.... https://github.com/NathanWalker/angular-seed-advanced I really hope I've been of any help.... Lars |
ping me in the community slack (https://nativescriptcommunity.slack.com/) if you still have that problem |
Dear @sis0k0 Stanimira,
I have tried and tried, but I don't get your samples to start within the 4 or 5 seconds on my Android. And really, I have tried well over a day to get it to work... What is your guess? Will this speed up in the near future? Or what is your guess that I am not doing well?
(The thing is - I need to deliver my project before end of may....)
In advance, many thanks for your time!!
The text was updated successfully, but these errors were encountered: