3 ms·
Your best bet is no integration at all. Just set up webpack to read from ./app/assets and output to ./public. Run it separately, preferable with a foreman Procf
by timdorr 11y ago
Your best bet is no integration at all. Just set up webpack to read from ./app/assets and output to ./public. Run it separately, preferable with a foreman Procfile for development (I've used Procfile.dev before).
- lucisferre 11y agoYou'll still likely want digested assets that integrate with Rails asset helpers. This has been done with Gulp[1] if that helps at all. [1]: http://viget.com/extend/gulp-rails-asset-pipeline http://viget.com/extend/gulp-rails-asset-pipeline
- danmaz74 11y agoThanks for the suggestion. I'd prefer some more automation, but that's also a possible solution.
- bl4ckdu5t 11y agoAnd what will the output to ./public be like? If webpack is using it's own cache busting asset links, how do we use that against sprockets? I think I'll just still stick to Grunt/Browserify