Sprockets is barely maintained for something that was and seemingly still is central to web apps. It’s needed for the images / CSS part of the asset pipeline. For example, it’s got a parallel execution hang that could be fixed by one line of reconfig, but it’s still in there to confuse the multitud…

Webpack integration makes reloading a page slower at this point. I’d be interested to hear if you have any profiling info to share (here are some debugging tips and some ideas for improving webpack performance ). I haven’t observed the same slowness with webpack relative to Sprockets (if anything,…

[image] rossta: I’d be interested to hear if you have any profiling info to share I do not have profiling info to share at this point, but if I get some, I will share it. Thanks for the links.

I use to import third party themes from my project and using Sprockets everything used to work smoothly but now it’s rather difficult. Furthermore I have to change a lot in the javascript of the theme to use webpacker instead with sprockets I didn’t need to change almost anything. I’d love if both S…

[image] Noel_Rappin: I agree that an up to date Rails Guide on Webpacker would be a big help. Even if it just duplicated the Webpacker readme, it’d be easier to find in Rails Guides… Existing guides also need to be edited. Existing guides still talk, sometimes in passing sometimes directly, a…

Thanks for inviting this kind of feedback. Webpacker succesfully makes using modern JS toolchains in Rails way easier than before Webpacker existed. But it is still really confusing. Some specific issues: The Guides still don’t mention webpacker at all as far as I know. The Guides have been a r…

Thanks! note that all my comments weren’t necessarily doc-related – I’m not totally sure which ones are solved by docs and which ones are solved by code, the first step is just the pain point!

There’s also some related discussion in Sprockets abandonment , particularly around the technical constraints that are leading the projects to be maintained in parallel. Mind if I merge this thread under that one?

@Betsy_Haibel please do what you think is best!

I have/had the exact same experience, could not have written it any better. I’m slowly coming to terms with “the new way” of handling assets, but you are absolutely right about this being an area where Rails should lead the way, just like in the past.

Sprockets abandonment

A May Of WTFs

Betsy_Haibel (Betsy Haibel) May 14, 2020, 5:43pm 59

Thanks for speaking up! @Noel_Rappin is stepping up as a champion for improving documentation around this and is coordinating that work in this thread: JavaScript Documentation Coordination - #8 by Noel_Rappin. If you have time to pitch in, I’m sure he’d appreciate the help.

Topic		Replies	Views
Webpacker presents a more difficult OOB experience for JS Sprinkles than Sprockets did A May Of WTFs webpacker	33	8419	February 7, 2021
JavaScript Documentation Coordination A May Of WTFs	21	3194	June 11, 2020
Asset management: webpacker vs sprockets, and docs, and sprockets A May Of WTFs	2	936	May 14, 2020
Current state of Webpacker rubyonrails-core	21	2834	February 27, 2022
Guide to Rails 7 and the Asset Pipeline rubyonrails-talk asset-pipeline	28	29659	January 10, 2024

Sprockets abandonment

Related topics

More Resources