New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support for CSS autoprefixer gem #67
Comments
Cool. Don’t forget add Jekyll How To to Autoprefixer’s README, when you will release it :). |
Autoprefixer's docs instruct simply to install |
@ajkochanowicz simple as that. Jekyll Assets tries to require the
|
@nz Thanks, so the output CSS should already have prefixes (where applicable) without any other steps? This isn't happening on my end. |
Are you sure I don't need to create a converter plugin as well? http://jekyllrb.com/docs/plugins/ |
It seems like you would also need to add the two gems to _config.yml per the jekyll docs. I did that, but still no success. |
@ajkochanowicz did you have any luck with this? I'm having the same issue. |
As part of my roadmap for 1.0 release all 3rd-party integrations are moved out of the core (by different reasons). So, if you are using master branch and not latest stable release, you won't have any integrations like bourbon or compass out of the box. You will need to either setup integrations yourself with ::Jekyll::Assets.configure do |assets|
assets.append_path "some path to compass assets"
end Or, in case of Autoprefixer, you can use jekyll-assets-autoprefixer gem to do all the magic for you. NB This instructions are valid for master branch only. If you are using stable release ( |
If you are experiencing troubles with
If you need to tune-up autoprefixer config, create |
Hm, having the same problem...
I added
No prefixed output for Using Autoprefixer with Jekyll looks more promising. |
If you are 1.0.0 then there is nothing we can do for you as it's legacy that is unless somebody wants to send a pull request to the legacy branch. However if you are on 2.0.0.pre.beta1 then all you need do is install autoprefixer-rails and it will enable autoprefixing for you. |
To add another note, just like autoprefixer-rails with Rails, you need to have a JavaScript runtime available too, NodeJS or TheRubyRacer are preferable. TheRubyRhino tends to have issues with NodeJS stuff. |
It doesn't work for me since Jekyll 3. Anyone else ? (before I spend hours debugging ;)) |
Then update to the beta version. |
of Jekyll ? or autoprefixer-rails ? or jekyll-assets ? |
@aastudio jekyll-assets, use the beta version from RubyGems or master from your Gemfile and you'll get autoprefixer support by just installing the Gem: https://github.com/jekyll/jekyll-assets#addons |
I've been having trouble for a couple days trying to get autoprefixer working. I'm probably doing something obvious wrong, but after browsing documents and issues for In my
In my
I tried adding to the autoprefixer configuration, even though docs show this shouldn't be necessary
My file structure is default for Jekyll
I still can't get it to work though. Any help would be much appreciated. |
In what location should the _config.yml file be placed? |
The CSS autoprefixer gem looks great, and it can be used by Sprockets as a CSS post-processor. Seems like a nice addition for jekyll-assets to lazily include if the gem is present in the load path.
https://github.com/ai/autoprefixer-rails
I have a local fork that's just dynamically injecting in the
Jekyll::AssetsPlugin::Environment#initialize
method if it canrequire
the gem:That gets the job done without much fuss, though there may be a better way. Happy to whip this up into a proper pull request if I can get some guidance on a more modular place to hook in to the Sprockets environment object.
The text was updated successfully, but these errors were encountered: