Differential loading is not working with ng serve / ng build --watch command

[SathyaChenniappan]

Differential loading is not working with ng serve/ng build --watch command. I am using angular 8.

[suhasdeshpande]

First one is generated when I build the project without watch mode.

This one's with watch mode and it does not create differential bundles. Is this expected behavior or bug?

[mgechev]

Since we want to speed up the development round trip time, it's intentional to not have differential loading on ng serve.

@alan-agius4 can comment about ng build --watch.

Is there any particular reason you need differential loading on ng serve?

[alan-agius4]

Hi, yeah it is expected that —watch will not trigger differential loading, the main reason for this that we are running builds sequentially which would make the watch experience slower.

[suhasdeshpande]

Alerts
I don't have a very good reason for asking this.

I am in process of migrating angularjs project over to CLI. Our Frontend is served using Rails assets pipeline and Frontend has very tight coupling with Rails. Reason to use watch is so that I can still get reasonable updates when I change Angular code but at the same time don't have to modify my hand-written script tags in Rails ERB template. I understand why this should not be the case but it would be nice if I can provide a flag knowing I will have slower experience to get the same bundles during this process.

[mgechev]

Just to make sure I understand, you use this process for development, right? Why is differential loading crucial in the process? Why you can't use only the ES2015 output?

[suhasdeshpande]

Purely development.

On Thu, Jun 27, 2019 at 4:11 PM Minko Gechev ***@***.***> wrote: Just to make sure I understand, you use this process for development, right? Why is differential loading crucial in the process? Why you can't use only the ES2015 output? — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#14911?email_source=notifications&email_token=AAET7V4WFB7VP3HHRS4MIOTP4VCIZA5CNFSM4H3VREHKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODYYTWLY#issuecomment-506542895>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAET7V2SLATIPZ4UUS3V3OTP4VCIZANCNFSM4H3VREHA> .

-- Software Engineer | Mode | [email protected] Front-End scripting

[cafesanu]

Hi @mgechev, the main reason at least for me is that we test locally ie11 via browserstack before we deploy. Is there a way to do this? I tried ng serve --prod but it still doesn't work

[mgechev]

@cafesanu you can build the app (ng build --prod) and serve it with any static web server (for example serve, serve -s dist/[project-name])

[cafesanu]

Thanks @mgechev. Yeah that's is what we've been doing. The only issue is that the dev cycle gets really slow this way as every single change needs the app to be built from scratch, so I end up wasting a lot of time (plus no sourcemaps, although I thing --source-maps would do the trick).

I totally understand your comment "we want to speed up the development round trip time", but the ironic part is that when we are testing ie11 (not all the time) then the dev cycle becomes painfully slow. I think it should of course not be the default with ng serve, but a flag, something like ng serve --diff-loading would be super nice

[angular-automatic-lock-bot]

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

_{This action has been performed automatically by a bot.}