[10.x] Add content method to Vite

[michael-rubel]

About

This PR adds a method to retrieve compiled content for the given file available in the Vite manifest. It allows us to pack our Vite assets inline when needed.

Example use case

You want to create an HTML page that needs to be open or sent as a single document (for example, as a mail attachment), and to work offline (without access to the internet) so the asset should be injected into the document for the browser to work on the local file without firing the HTTP requests.

Usage example

<style>{!! Vite::content('resources/scss/file.scss') !!}</style>

[jessarcher]

This sounds pretty useful, and I've run into similar scenarios myself.

My only concern is that the local dev behaviour might be unexpected or confusing when running the Vite dev server. It will fail if you haven't run a build since adding the asset. Otherwise, it will return the contents from the last build, ignoring any changes you've made to the source file. You'd need to run Vite in "watch" mode instead of HMR mode if you wanted to automatically have the latest changes while developing.

[michael-rubel]

@jessarcher what can we do to address this? Maybe adding an exception when in HMR and the method is called?

By the way, developers can add a check like this:

@if (! Vite::isRunningHot())
    <style>{!! Vite::content('resources/scss/file.scss') !!}</style>
@else
    @vite('resources/scss/file.scss')
@endif

I thought also about adding the redirect to the Vite::asset() when the HMR mode is enabled, but that would require lots of additional work on the framework side, and not sure it's worth it or makes sense. The way it is now it can be kept simple.

[jessarcher]

@michael-rubel You could try calling file_get_contents on the dev server URL for the asset, but I'm not sure how well that would work. For something like CSS, it might be okay. But for JavaScript, it might cause more issues and confusion than it solves 😅

It's probably fine as-is. Just a caveat to be aware of when using it.