In dev, when running a rails console or bin/rails server, the manifest is already loaded (because of the Rails::Server and Rails::Console definition checks). But in some environments (e.g. when booting the server through Puma), those constants aren't defined, but we still want to eagerload the manifest.
The PR is still in draft as I dig into why the constants aren't always defined.
Description 📖
Ensures the ViteRuby manifest is eager loaded, following the Rails pattern (similarly to https://github.com/tzinfo/tzinfo/commit/c4f177c4808c11aa28f87fb3b452f832342c970c).
In dev, when running a rails console or
bin/rails server, the manifest is already loaded (because of theRails::ServerandRails::Consoledefinition checks). But in some environments (e.g. when booting the server through Puma), those constants aren't defined, but we still want to eagerload the manifest.The PR is still in draft as I dig into why the constants aren't always defined.