Continued Sage 10 cleanup

[Log1x]

Changelog

Enhancements

• Add name configuration to config/app.php (defaults to theme name).
• Move default cache location to storage/.
• Add a ServiceProvider stub.
• Add missing trailing commas to configs.
• Remove/revert automatic Blade cache removal action as it is no longer necessary.
• Clean up .gitignore.
• Clean up JavaScript docblocks.
• Remove home.js example leaving about.js to give an example of camelCase.
• Remove leftover Sage 9 information from the readme.

Todo

• Move the DOM-based router to it's own package.
• Change Acorn's manifest/asset class to handle leading slashes.
• Figure out a solution to handle images and fonts versioning (attempt a PR into Laravel Mix?)
• Decide on a solution for changing cache busting from args to filenames (laravel-mix-versionhash or attempt a PR into Laravel Mix).
• Update documentation for Sage 10.
• Write a changelog.
• Bump Add wp_body_open hook (WP 5.2+) #2167 for when 5.2 releases.
• Sage CLI (probably after release?)

[LeoColomb]

• Figure out a solution to handle images and fonts versioning (attempt a PR into Laravel Mix?)
• Decide on a solution for changing cache busting from args to filenames (laravel-mix-versionhash or attempt a PR into Laravel Mix).

👍

I have been compiling assets via laraval-mix for years now, even for Sage based projects, and file-versioning is the main drawback.

In both case I would support you opening a PR on the Laraval Mix repo, but the maintainer is difficult to convince for this kind of option.
See:

• Work In Progress: Opt-in filename based versioning laravel-mix/laravel-mix#1470
• How to config use file hashing instead of query strings ? laravel-mix/laravel-mix#934
• Option in version() to choose querystring or file name with hash laravel-mix/laravel-mix#1241
• Versioning no longer Load Balancer friendly laravel-mix/laravel-mix#1022

For standalone images, we can use mix.version([...paths]).