So that's what Propshaft doesn't do. Here's what it does provide:
- Configurable load path: You can register directories from multiple places in your app and gems, and reference assets from all of these paths as though they were one.
- Digest stamping: All assets in the load path will be copied (or compiled) in a precompilation step for production that also stamps all of them with a digest hash, so you can use long-expiry cache headers for better performance. The digested assets can be referred to through their logical path because the processing leaves a manifest file that provides a way to translate.
- Development server: There's no need to precompile the assets in development. You can refer to them via the same asset_path helpers and they'll be served by a development server.
Basic compilers: Propshaft was explicitly not designed to provide full transpiler capabilities. You can get that better elsewhere. But it does offer a simple input->output compiler setup that by default is used to translate
url(asset)function calls in CSS to
url(digested-asset)instead and source mapping comments likewise.
With Rails 7+, you can start a new application with propshaft using
rails new myapp -a propshaft. For existing applications, check the upgrade guide which contains step-by-step instructions.
Propshaft makes all the assets from all the paths it's been configured with through
config.assets.paths available for serving and will copy all of them into
public/assets when precompiling. This is unlike Sprockets, which did not copy over assets that hadn't been explicitly included in one of the bundled assets.
You can however exempt directories that have been added through the
config.assets.excluded_paths. This is useful if you're for example using
app/assets/stylesheets exclusively as a set of inputs to a compiler like Dart Sass for Rails, and you don't want these input files to be part of the load path. (Remember you need to add full paths, like
These assets can be referenced through their logical path using the normal helpers like
assets:precompile has been run (through a JSON mapping file found in
Bypassing the digest step
-[digest].digested.js as the postfix to any asset file as an indication that the file has already been digested.
Migrating from Sprockets
Propshaft does a lot less than Sprockets, by design, so it might well be a fair bit of work to migrate if it's even desirable. This is particularly true if you rely on Sprockets to provide any form of transpiling, like CoffeeScript or Sass, or if you rely on any gems that do. You'll need to either stop transpiling or use a Node-based transpiler, like those in
But for greenfield apps using the default import-map approach, Propshaft can also work well, if you're able to deal with vanilla CSS.
Will Propshaft replace Sprockets as the Rails default?
Most likely, but Sprockets need to be supported as well for a long time to come. Plenty of apps and gems were built on Sprocket features, and they won't be migrating soon. Still working out the compatibility story. This is very much alpha software at the moment.
Propshaft is released under the MIT License.