Thank you to everyone who has contributed to Webpacker over the last five-plus years! But Justin Gordon is continuing that line of development – including a focus on hot-module reloading features etc – under a new gem called Shakapacker that is based on the unreleased v6 work from this repository. The development of v6 will not result in an official gem released by the Rails team nor see any future support. This pertains to the v5 edition of this gem that was included by default with previous versions of Rails. But we will not be updating the gem to include newer versions of the JavaScript libraries. We will continue to address security issues on the Ruby side of the gem according to the normal maintenance schedule of Rails. This will output the following result: webpack 5.31.2 webpack-cli 4.6.0. That's the default setup for new Rails 7 applications, but depending on your JavaScript use, it may be a substantial jump.įinally, you can continue to use Webpacker as-is. To inspect the version of webpack and webpack-cli you are using, run the command: npx webpack -version or npx webpack version. Secondly, you may want to try making the jump all the way to import maps. You can follow the switching guide, if you choose this option. We now have three great default answers to JavaScript in 2021+, and thus we will no longer be evolving Webpacker in an official Rails capacity.įor applications currently using Webpacker, the first recommendation is to switch to jsbundling-rails with Webpack (or another bundler).
This bridge is no longer needed for most people in most situations following the release of Rails 7. Webpacker has served the Rails community for over five years as a bridge to compiled and bundled JavaScript.
0 kommentar(er)
