I like how the Rails Asset Pipeline gives you a single CSS artifact with a cache-busting hash in the name, but I've been trying to use Webpack for some new projects and I was surprised to learn that by default it doesn't create any CSS file, but embeds the CSS in Javascript and injects it at runtime. Is that considered better nowadays? What are the pros and cons? I Googled around a bit but didn't find any answers.
Btw here is a sample webpack config that uses ExtractTextPlugin to get behavior more like the Asset Pipeline, including pulling in Bootstrap and getting correct font references. Maybe someone can use it:
I am playing around with http://bulma.io which is based on flexbox. Only complain is that they don't use https on their marketing site yet :) but otherwise, looks like a great clean framework.
Same. I work on such a diverse number of projects and codebases (from diverse sources) that I've found it best to stay as grounded in regular CSS as possible.
[+] [-] jachee|8 years ago|reply
[+] [-] rgera|8 years ago|reply
[+] [-] pjungwir|8 years ago|reply
Btw here is a sample webpack config that uses ExtractTextPlugin to get behavior more like the Asset Pipeline, including pulling in Bootstrap and getting correct font references. Maybe someone can use it:
https://github.com/pjungwir/webpack-bootstrap-test
[+] [-] codegeek|8 years ago|reply
[+] [-] romanovcode|8 years ago|reply
[0] https://picturepan2.github.io/spectre/index.html
[+] [-] companyhen|8 years ago|reply
[+] [-] sjs382|8 years ago|reply
[+] [-] txmjs|8 years ago|reply
[+] [-] Slaul|8 years ago|reply
[+] [-] 02thoeva|8 years ago|reply
[+] [-] tmaly|8 years ago|reply
I am using the flexbox aspect of the framework called Neat.
[+] [-] wprapido|8 years ago|reply
[+] [-] hueyl77|8 years ago|reply
[+] [-] hfourm|8 years ago|reply
[+] [-] oblib|8 years ago|reply