Migrate from Laravel Mix to Vite

[PhilReinking]

This pull request includes changes for migrating from Laravel Mix to Vite outlined in Migration Guide and automated by the Vite Converter.

Before merging, you need to:

• Checkout the shift-76370 branch
• Run composer update
• Run npm install
• Review all comments for additional changes
• Thoroughly test your application (no tests?, no CI?)

Please send your feedback to shift@laravelshift.com or share the good vibes on Twitter.

[PhilReinking]

:information_source: Previously, Laravel configured several npm scripts for building assets. For Vite, Laravel configures a dev script for generating and watching your assets (for development) and build script for generating your assets (for production).

Shift automated this change by replacing commands using these scripts with their new Vite script. However, you may still be referencing these scripts in your code or in deployment scripts.

[PhilReinking]

:warning: Shift detected you are using Vue. As such, Vite recommends importing your CSS from your JavaScript entry point. This will improve you development experience by avoid flashes of unstyled content during hot reloading.

Shift removed your CSS entry point from your Vite configuration. However, you will need to import this CSS in your JavaScript entry point.

[PhilReinking]

:informationsource: Laravel renamed the environment variables used by Mix to use a `VITEprefix, instead ofMIX_`. While Shift automated this change throughout your code, you should check for any additional references which may not be included in your Git repository.

[PhilReinking]

:warning: Vite generates frontend assets to the public/build folder. This folder is not tracked by Git within a default Laravel project. As such, Shift added this folder to your .gitignore file.

If you wish to track the generated frontend assets within your project, such as for ease of deployment, you may undo this commit by running git revert 9bcb6036.

[PhilReinking]

:warning: Shift detected you are using Inertia. You may need to update your require statement for Vue components as well as configure an entry point if you are using SSR.

[PhilReinking]

:information_source: The new @vite Blade directive outputs <script> tags with the type="module" attribute. This attribute implicitly defers the script. This is a difference from Laravel Mix which may change the execution order of the JavaScript on your page.

If you experience JavaScript errors relating to undefined references, you may need to reorder your scripts or add the defer attribute to any inline <script> blocks on your page.

[PhilReinking]

:alembic: This Shift is still being refined. Please report any issues or suggestions to shift@laravelshift.com. Your feedback is what helps improve the experience for everyone.

[CLAassistant]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.
1 out of 2 committers have signed the CLA.

:white_check_mark: PhilReinking
:x: laravel-shift
_{You have signed the CLA already but the status is still pending? Let us recheck it.}

[what-the-diff[bot]]

• Update Laravel to 9.19
• Remove laravel-mix and replace with vitejs
• Add autoprefixer for css files in production build (vue plugin)
• Fix imports of Jetstream components from .vue file extension instead of directory name, since we are using the ViteJS plugin now which doesn't support this out of the box yet: https://github.com/deck9/ui/issues/8#issuecomment-749095697

[PhilReinking]

Probably does work for development and self-hosted now. But could not figure out how to make the classic.js (form frontend) combine into one JS bundle including the CSS. Having it split in chunks and optimized, might it make more difficult to distribute.

Also need to get rid of the file hash for the classic.js

[PhilReinking]

Figured out the bundling of classic.js. I think we can move forward with this. Will not include it in the latest release.