iskin

9 ms·

61.
by iskin 10y ago
Main reason to use PostCSS is not to replace preprocessor. Main revolution happens outside a syntax-sugar world right now. This is why main reason to use PostCSS is to have non-preprocessors tools: 1. Autoprefixer. 2. Stylelint. Like ESLint
62.
by iskin 10y ago
If you asked about PostCSS-based preprocessors (it is small part of PostCSS features) — there is a 2 solutions: * postcss-cssnext, preset of CSS drafts polyfills. It is not 100% preprocessor, but because of CSS custom properties and CSS nes
63.
by iskin 10y ago
PostCSS is a framework to create a CSS tools. Preprocessors (Sass/Less) is only one type of tools that you could build on top of PostCSS. So using PostCSS != not using Sass. You could use Sass for processors, but still using PostCSS fo
64.
Animakit: wrap your React components to get animations for better UX(animakit.github.io)
13 points by iskin 10y ago|0 comments
65.
How PostCSS became 1.5x faster by changing 2 lines of code(evilmartians.com)
55 points by iskin 11y ago|28 comments
66.
Convert-layout.js fixes wrong keyboard layout in user inpput(github.com)
7 points by iskin 11y ago|0 comments
67.
Autoprefixer 6.1 is out with CSS-in-JS and :read-only support(github.com)
44 points by iskin 11y ago|18 comments
68.
This best plugins for PostCSS(medium.com)
7 points by iskin 11y ago|0 comments
69.
Autoprefixer 6.0 is out with PostCSS 5.0 and many new prefixes(github.com)
9 points by iskin 11y ago|0 comments
70.
Autoprefixer 5.2 is out with appearance support, warnings and 30% faster(github.com)
2 points by iskin 11y ago|0 comments
71.
Postcss-Spiffing: Write CSS in British English(github.com)
2 points by iskin 12y ago|0 comments
72.
PostCSS 3.0 is out with the fastest JavaScript-based CSS parser(github.com)
2 points by iskin 12y ago|0 comments
73.
by iskin 12y ago
I use Sass with postprocessors. They are not enemies. Sass and preprocessors are better to fix CSS syntax. Postprocessors are better for some automatically task, like autoprefixing, media queries packing, polyfills, etc. Unfortunately, Sass
74.
PostCSS 1.0: Framework for CSS post-processors with full source map support(github.com)
6 points by iskin 12y ago|3 comments
75.
Autoprefixer 1.2 “Meiji” was released(github.com)
1 points by iskin 12y ago|0 comments
76.
Autoprefixer 1.1 was released(github.com)
1 points by iskin 13y ago|0 comments
77.
Autoprefixer 0.6 is 50 times faster than Compass and 10 times faster than Stylus(github.com)
1 points by iskin 13y ago|0 comments
78.
Autoprefixer is a tool to parse CSS and add vendor prefixes by Can I Use(github.com)
2 points by iskin 13y ago|0 comments
79.
Autoprefixer - parse CSS and add prefixed by actual Can I Use database(github.com)
2 points by iskin 13y ago|0 comments
80.
by iskin 14y ago
Idea behind Rework (real preprocerssor, not language) is better and more flexible https://github.com/visionmedia/rework
81.
by iskin 14y ago
Unlike Ruby on Rails build-in I18n library, R18n autodetect user locale (for Rails, Sinatra and desktop apps), translate models or any objects, has flexible filters, use better locales architecture, can load translations by any way (files,
82.
R18n 1.0.0, i18n for Rails/Ruby(github.com)
3 points by iskin 14y ago|2 comments
83.
by iskin 14y ago
Nice. I often miss error on long deploy, because I hide terminal window.