If you are familiar with Sprockets, the following guide might give you some idea of how to translate. You should choose Sprockets over Webpacker for legacy applications where migration might be costly, if you want to integrate using Gems, or if you have a very small amount of code to package.
You should choose Webpacker over Sprockets on a new project if you want to use NPM packages and/or want access to the most current JavaScript features and tools. New Rails apps are configured to use webpack for JavaScript and Sprockets for CSS, although you can do CSS in webpack. However, webpack is better at integrating with more current JavaScript tools and NPM packages and allows for a wider range of integration. In particular, code can be added to Sprockets via a Ruby gem. Sprockets, which was designed to be used with Rails, is somewhat simpler to integrate. In a development environment, Sprockets and Webpacker allow you to incrementally change files. Both tools will compile your JavaScript into browser-friendly files and also minify and fingerprint them in production. Rails also ships with Sprockets, an asset-packaging tool whose features overlap with Webpacker. 1.2 How is Webpacker Different from Sprockets? See the webpack documentation for information. Webpack will allow you to write your code, reference other code in your application, transform your code, and combine your code into easily downloadable packs. With webpack, you can manage JavaScript, CSS, and static assets like images or fonts. The goal of webpack, or any front-end build system, is to allow you to write your front-end code in a way that is convenient for developers and then package that code in a way that is convenient for browsers. I'll dig around a bit more and see if I can simplify reproducing this.Webpacker is a Rails wrapper around the webpack build system that provides a standard webpack configuration and reasonable defaults. So the problem does seem to be related to builder but isn't triggered when I install builder directly.
0 kommentar(er)
