Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What is the goal of this PR and why is this important?
Add and configure vite-rails.
Vite is modern asset builder / bundler that we will use for
javascript and CSS assets going forward.
This also enables a second rails docker container that acts
as an asset host, supporting live reloading within the rails
application structure.
As it currently stands, the now-legacy sprockets / asset pipeline
configurations are loading at the same time within the main application
layout. We may want to consider having two separate layout pages and
using that in building out new functionality, and opting-in legacy pages
when they've migrated away from using the features of the old asset pipleine
How did you approach the change?
Anything else to add?