Sometime emoji's would randomly not render due to VueJS being reactive
and during DOM updates, it would just cause it to be wacky!
By parsing the emoji's server side before VueJS renders the dom, we now
solve this issue.
ref: https://laravel.com/docs/5.6/mix
We will now handle assets primarily through packages.
Consider packages and node modules to be the same as
JavaScript/CSS libraries.
Think about it this way, if we use "composer" to import PHP packages
for backend libraries, we would then use "npm" to import JS/CSS packages
for front-end libraries.
We use "composer.json" for PHP packages and "package.json" for JS/CSS
packages.
Unlike composer, we will compile our assets into specified files
per instructed via the "webpack.mix.php" file.
Please Note, you don't version control "node_modules" nor need it in a
production environment! You do NOT edit any of the JS/CSS files in the
public directory!
With Laravel Mix using simple method chaining, you can fluently define
your asset pipeline.