sprockets-rails icon indicating copy to clipboard operation
sprockets-rails copied to clipboard

Sprockets Rails integration

Results 81 sprockets-rails issues
Sort by recently updated
recently updated
newest added

When the [--public-path option was added to esbuild](https://github.com/rails/jsbundling-rails/pull/58) it broke Sprockets's ability to resolve sourcemaps, even though they're still present. Esbuild's sourcemap output with `--public-path=assets`: `//# sourceMappingURL=assets/application.js.map` Esbuild's sourcemap output...

Esbuild puts the `publicPath` as a prefix in the `sourceMappingURL` and because I am using `editor/editor` to generate the script tag sprockets-rails generating the wrong path and removing the `sourceMappingURL`...

# Description Sprockets gem appends semicolons to each js asset which corrupts `//# sourceMappingURL=` magic comments. `sprockets-rails` fixes this by appending `\n//!\n` to the asset so the `sourceMappingURL` is not...

Until 2.3.3, it was ok to do image_tag('image') From 3.0, to avoid getting the AssetsNotPrecompiled error, you need to mandatorily specify the file extension .... image_tag('image.png') Again, not a big...

We have a JS asset that contains some generic polyfills from [@babel/polyfill](https://github.com/babel/babel) From this [Sprockets v3.4.0 update](https://github.com/rails/sprockets-rails/pull/479/files), our application stopped working We found the issue occurs when we use `source-maps`...

Previously only javascript files had their sourceMappingURL comments rewritten with the digested asset location. This PR adds the same treatment to sourceMappingURL comments in css files

Processor is great but it only supports JS convention at the moment. When I generate compressed CSS with dart-sass, sourcemapping URL comment looks like following ( ```/*# sourceMappingURL=application.css.map */``` Unfortunately,...

Hello, This is more of a suggestion in order to improve developer experience if possible. I ran into an issue earlier where a `cp -r` command within a Docker file...

At first glance this might be an obvious statement, however if you happen to end up with a config that falls through the below setup routine and ends up with...

@jrochkind adds language to README: "It no longer necessary to use eg asset-url() helper (which was introduced by sass-rails). All `url(...)` references in CSS are just transparently processed to use...