Alex Eimer

Also the security aspect is interesting: 

We write a learning platform for informatics, I wouldn't care about IE11. But it should work on Edge,,,

Do I see it correct, that this makes only sense if you squash the commits on merge, which I definetly wouldnt recommend for this project?!

So I would suggest to close this issue...


@chrismellard is this ticket already closed? I guess, as the PR #1629 is merged?!

As we only want to deploy specific parts (like hooks, actions and in a second repo only the html templates) this setting would make our setup more resilient against new...

I can replicate this with npm and a two stage build, but it happens in the first stage: ``` INFO[0048] Saving file app for later use INFO[0050] Saving file app/dist...

Great. Many thanks!

@kevcenteno can we tag the new version and deploy it therefore?