Multiple enhancements and fixes / Repair and speeding up Travis CI builds

[TemaSM]

• Updated sweetalert2 from ^7.19.3 to ^8.10.0
• Updated vue-router, vue-i18n, jquery, sass, eslint-plugin-import, eslint-plugin-node
• Forced Laravel Dusk to use latest stable Chrome driver release (it was one of many reasons why Travis CI failing tests)
• Enhanced Travis CI config - caching composer and npm, selfupdating composer, nodejs & npm to latest stable release during build, speeding up
• Improved Laravel Dusk tests (fixed no such element: Unable to locate element and element not interactable)
• Temporary disabled mix.extract(), because it's buggy with Webpack code-splitting/chunking mechanism (dynamic imports), see commit addf76d and related issue Extracted files path issue when using extract() and chunkFilename.. laravel-mix/laravel-mix#1889
• Refactored routes file & fixed bugs of Laravel Mix 4 in webpack.mix.js file
• Made HMR mode work great again, fixes HMR #163
• Regenerated composer.lock for freshness

[TemaSM]

Travis CI failing because Laravel Dusk has old Chrome driver, according to laravel/dusk#641 issue.
So, there are incompatibility between chromedriver=2.45.615279 and Unpacking google-chrome-stable (74.0.3729.108-1) over (62.0.3202.94-1) as seen in Travis CI logs: Facebook\WebDriver\Exception\SessionNotCreatedException: session not created: Chrome version must be between 70 and 73

[TemaSM]

According to Travis CI logs, eacf717 commit helped with Chrome and its driver to be in sync of versions to process Dusk tests

[TemaSM]

Finished with this PR, so waiting for your review @cretueusebiu

[cretueusebiu]

Thanks for all the great work! Will merge it soon.

[TemaSM]

Great to hear.
There're some minor/patch updates available for npm & composer dependencies, so will update them in an hour, just for better freshness of laravel-vue-spa.

[cretueusebiu]

I see you added clean-webpack-plugin, do you know if there's a way to clear the files after the build process, because right now when you run npm run prod it will delete the files and then generate new ones. So if your app is in production, for a few seconds while it builds, the js/css files will be missing.

[TemaSM]

Yeah, probably that's not good behavior. Will try to improve the way of clean rebuilding frontend & its assets. ETA: 1 hour.

[TemaSM]

Found bug with Laravel Mix and Webpack chunks (in vue-router routes definition file).
Fixing may take more time than I expected.

[cretueusebiu]

It's really a bummer with Laravel Mix 4. There seems to be so many new bugs introduced... Should we wait a bit more for a new release of Mix or maybe go back to v2 ?

[TemaSM]

I think we can stand with v4 by applying few codehacks for building process (fixed few already) and release new laravel-vue-spa.
But will remove them, just after Laravel Mix developers fix bugs.
If my attempts to fix will unsuccessful, then downgrading to v2 will be the best option I think.

[TemaSM]

I made it working fine, but there's still bug with HMR mode.
Can push commit, so you may test everything except HMR, till I trying to fix it too.

[cretueusebiu]

Great! HMR didn't worked before too, so that's not a problem.

[TemaSM]

That's it, fixed all bugs of Laravel Mix, even HMR mode 😃
Waiting for your review @cretueusebiu

P.S> Probably, I have a better solution for fixing #153 than #155 PR.
Will try to do my best, but in different PR, right after we merge this one.

[cretueusebiu]

Great job with this PR!

I've made some minor changes and will tag a new release soon.