Skip to content
This repository was archived by the owner on May 1, 2020. It is now read-only.

Create Notion of Production/Release Build #299

Closed
danbucholtz opened this issue Nov 2, 2016 · 6 comments
Closed

Create Notion of Production/Release Build #299

danbucholtz opened this issue Nov 2, 2016 · 6 comments

Comments

@danbucholtz
Copy link
Contributor

  1. Discuss removing minificaction from development build to device
  2. Include sourcemap for development build to device
  3. Create a --release or --prod argument that does minification, etc.

Questions:
Should we always do AoT when deploying to device?

@PhilippRath
Copy link

Is AoT always necessary on debug / dev build, if we had a switch, this would be nice.

i mean you will definitely have the ability to test it, but for faster development, i would like to skip this compiling stuff.

is this related to the issue with the 0.39 app-script Version issue that emulate builds are always Production

ionic emulate android --debug --dev
--------------------------------

Running 'emulate:before' npm script before emulate

> ionic-hello-world@ build /Volumes/DATEN/repositorys/tmp/httpGettest/httpGetTest
> ionic-app-scripts build

[09:15:35]  ionic-app-scripts 0.0.39 
[09:15:35]  build prod started ... 

@danbucholtz
Copy link
Contributor Author

@rathgeber2, you can pass the --dev option to skip AoT which will speed things up. We are working with Angular on getting an incremental AoT build in place. Google internally has sub-second AoT builds so some members of the Angular team are going to be working on better tooling to make this possible for the broader community. Fingers crossed that is happens soon!

Thanks,
Dan

@NoNameProvided
Copy link
Contributor

Google internally has sub-second AoT builds so some members of the Angular team are going to be working on better tooling to make this possible for the broader community.

Wow! that incremental sub-second AoT builds is a must! Excited to have this!

Questions:
Should we always do AoT when deploying to device?

Yes, I think it's a good idea to default to that. The difference between an AoT compiled app and a normal one is huge on older devices which can make testing really painful.

Our current process is to test with AoT (I mean clicking around and using features) and when we find a bug we simply fix it in the browser environment and verify that fix when a few other bug was fixed as well. This approach is a way more faster for us than reloading the app all the time.

@danbucholtz
Copy link
Contributor Author

This is resolved.

Thanks,
Dan

@NoNameProvided
Copy link
Contributor

Does app-scripts supports incremental builds now?

@danbucholtz
Copy link
Contributor Author

No, ngc does not support incremental builds and there is no timeline for that. Production builds are going to be slow for awhile so the best bet is to just use development builds as much as possible.

Thanks,
Dan

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

4 participants