You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
New Rails 7 App with ESBuild, and Bootstrap. It works. OK. Great. Builds fine.
In the provided app/assets/stylesheets/application.bootstrap.scss file, if I were to add a single class of valid code to use an image, it all breaks. For example:
.test {
background-image: image-url("foo.jpg");
}
For whatever reason, when the sass command tries to build that, the build blows up with errors. Specifically, the long-ass fingerprint signature added to the asset is part of the error. Not sure why. It seems the helpers for sass are not being digested properly as per the old sassc-rails gem. So what is the modern way to go here?
What is the secret to using the needed helpers to get assets into Sass with the new setup and CSS Bundling gem?
The text was updated successfully, but these errors were encountered:
config.assets.resolve_assets_in_css_urls
When this option is enabled, sprockets-rails will register a CSS postprocessor to resolve assets referenced in [url()](https://developer.mozilla.org/en-US/docs/Web/CSS/url()) function calls and replace them with the digested paths. Defaults to true.
New Rails 7 App with ESBuild, and Bootstrap. It works. OK. Great. Builds fine.
In the provided app/assets/stylesheets/application.bootstrap.scss file, if I were to add a single class of valid code to use an image, it all breaks. For example:
For whatever reason, when the sass command tries to build that, the build blows up with errors. Specifically, the long-ass fingerprint signature added to the asset is part of the error. Not sure why. It seems the helpers for sass are not being digested properly as per the old sassc-rails gem. So what is the modern way to go here?
What is the secret to using the needed helpers to get assets into Sass with the new setup and CSS Bundling gem?
The text was updated successfully, but these errors were encountered: