Ref: OM26 / DECOM-6

Related to the upgrade to Rails 6, we need to migrate to webpacker, as this is the default way of handling javascript in Rails. See more information in the discussion at #6806, especially the great detective work by @alecslupu:

I have dug for the last few days in that rails 6 upgrade, and i think that Decidim is not ready yet for that ...

I have got into the same issue with the webpacker ( meaning that i have installed, but somehow the assets are getting messed up ) (Implementing the suggestion with webpacker in gem, i got into a strange situation when main/development app, tried to load assets from decidim. in my endeavors i have not been able properly load decidim packs in main app, nor provide a parameter that would specify the module / pack where the asset is located ) (edited)

from what i have seen, DHH stated that webpacker and sprockets can work together, after digging for about 2 days ... i could not find a way around that , so i have managed to look into other engines that are out there, and i have seen that they are using the assests pipeline ( sprockets )

From my investigations, in order to successfully upgrade to rails 6, we need to remove that sprockets-es6 compatibility (please read details here https://