Easily integrate an externally-managed asset pipeline with Rails
Support Rails 7.
Note: Sprockets is no longer an explicit dependency in Rails 7, so if your application still uses Sprockets (or Propshaft) then that railtie will now be loaded by Bundler.require(*Rails.groups)
in config/application.rb
(rather than by require "rails/all"
). As a result, it's important to place the require "external_asset_pipeline/railtie"
line after Bundler.require(*Rails.groups)
to ensure that ExternalAssetPipeline takes precedence over Sprockets (or Propshaft).
Consider manifest to be empty if the corresponding manifest file does not exist.
Add ExternalAssetPipeline::VERSION::MAJOR
, ExternalAssetPipeline::VERSION::MINOR
, and ExternalAssetPipeline::VERSION::PATCH
constants and rename ExternalAssetPipeline::VERSION
to ExternalAssetPipeline::VERSION::STRING
.
Default dev_server.host
setting to 'localhost'
and dev_server.port
setting to 3035
. This means there is less to configure in apps which align with these conventions.
Add external_asset_pipeline_manifest
helper method which can be overridden to return a different Manifest
instance than the default. One example use case would be to override this helper in different rails engines to use a distinct Manifest
instance in each one.
Add prepend_assets_prefix_to_manifest_values
setting to support manifests whose values already include the assets prefix.
Add dev_server.public_origin
setting to support the use case where different origins are used when the rails backend connects to the dev server (to get the manifest) and when the browser requests assets from the dev server.
Add support for requesting assets from a dev server
Initial version