Webpacker v6 is a great option for those who want to continue on that track. But it will no longer be bundled with Rails 7. The path we’re going with by default going forward is import maps (no Node required at all) and then jsbundling-rails as the step from there. But you don’t need anyone’s permission to continue to use Webpacker if you fancy. The gem will still be there, and v6 is a much slimmer fit than v5 was.
I’m super excited to ship v6!
Questions for the Community:
What can I do better as a moderator on rails/webpacker? Do we have guidelines for moderators of rails projects?
Who cares about the next version of rails/webpacker, and what else would you like to see?
What can I do to accelerate the release process? The uncertainty of the final details of rails/webpacker affects many projects.
As Justin mentioned, there’s no bandwidth in the Rails core group to continue to evolve Webpacker. All our energy is going into the two new defaults: jsbundling-rails and import maps. We will continue to support Webpacker v5 on the Ruby side according to the normal maintenance schedule.