Thanks again for taking the time to write a detailed answer.
What if I don’t use mix release?
Is there anything else preventing me or any other reason I should avoid to put the chromium binary in the assets directory?
Maybe we can implement an option where the user can chose either to save the packages to the priv or assets directory so that the user is not only dependent on global install of npm packages and can use local installation?
I’d be happy to open up a pull-request if there are no other reasons (besides mix release) to not have the chrome binary in /assets.
