Redundant check removed since compiled class file generation was removed
https://github.com/laravel/framework/commit/09964cc8c04674ec710af02794f774308a5c92ca#diff-7b18a52eceff5eb716c1de268e98d55dL870

Remove the hot file from versionning

Following https://github.com/laravel/framework/pull/17571, I was correctly pointed that the small proposition should be made over here. Here's a copy / past of my message, for clarity's sake.
---

When you run `npm run hmr`, a `hot` file is created to the public folder for the `mix()` helper to know if it has to server from the webpack server or not. This file does not go away until we run `npm run dev` (or `watch`). 

True, if we use `npm run production` in our production server it goes away too, but in case we don't make it go away in development, I don't think it's necessary to version it.

Ensure cross-env gets executed by node

Update composer.json to contain autoload-dev for Test namespace

Only autoload the tests namespace in dev.

Add missing path for Yarn Fix

Make scripts work with Yarn

Use const and destructuring assignment

Bump Mix dependency

Normally, words that start with vowels (like "unified") are preceded by "an" instead of "a."  However, "unified" is an exception to the rule.

Source: https://www.a-or-an.com/a_an/unified

[5.4] Change PUSHER enviroment variable names

[5.4] Remove compile.php

It's not used anymore.

Revert "[5.4] Change PUSHER enviroment variable names"

[5.4] Change PUSHER enviroment variable names

pusher.com's copy and paste .env snippet uses enviroment variables that
all start with "PUSHER_APP". This commit brings the config files in line
with pusher.com

These are very similar to routes in that they are channel endpoints
that your application supports and they also fully support route model
binding in Laravel 5.4. Upgraded applications do not need to make this
change if they do not want to.