|Number of watchers on Github||114|
|Number of open issues||11|
|Average time to close an issue||less than a minute|
|Average time to merge a PR||6 months|
|Open pull requests||0+|
|Closed pull requests||3+|
|Last commit||over 2 years ago|
|Repo Created||about 7 years ago|
|Repo Last Updated||over 2 years ago|
|Organization / Author||mrmrs|
|Do you use css-uncut? Leave a review!|
|View open issues (11)|
|View css-uncut activity|
|View on github|
|Book a Mock Interview With Me (Silicon Valley Engineering Leader, 100s of interviews conducted)|
Software engineers: It's time to get promoted. Starting NOW! Subscribe to my mailing list and I will equip you with tools, tips and actionable advice to grow in your career.
How big is the entire css language? Is it bigger or smaller than 500K?
So, what is css uncut? It is an attempt to put the entire css language in one file. For the most part it's a bunch of single purpose classes name spaced to three different breakpoints.
Plus a few other things like a clearfix solution for good measure.
The file sizes:
npm install --save-dev css-uncut
480K - i.css (uncompresed) 390K - i.min.css (minified) 47K - i.min.css.gz (minified & gzipped)
47K minified and gzipped. This gives in an interesting baseline to compare 500K+ css files to. It should be noted that gzip loves single purpose classes as it's compression algorithm works best when common words are close together. If you randomize the order of class declaration in i.css, it minifies and gzips down to 54K which turns out to be a delta of about 7K.
Some things would be almost impossible to represent in totality. Like gradient combinations for instance. But most things are pretty easy. Properties such as float, display, list-style-type, overflow etc. have a fairly small set of values. This has all of those things. Four times.
Some things are a bit trickier though. How many different border-widths should be included? What about border-colors? I tried to err on the side of being more verbose than I thought any feasible ui would need. In this case I chose to include 140 different border colors for congruency with the provided skin classes.
If it's in the spec, it's probably in here. If you notice anything missing. Please open an issue or file a pull request.
For each of the dimension properties i.e
width, max-width, min-width, height, max-height, min-height
There are classes for:
Skin classes for each of the 140 color names defined in the css/html spec.
Eight step scale for both margins and padding. Single purpose classes to target: all, top, right, bottom, and left sides as well as utilities to space horizontally and vertically. It's easy to extend if you need more or less steps.
Naming conventions. There are some nice grockable consistent patterns, but some of them aren't that well thought out to be honest. Particularly things like flexbox, animation, and transitions.
Selector count. I wouldn't advise dropping this into your next project in totality. There are more than 4096 selectors and that means certain versions of ie won't parse the whole style sheet. If you want to drop the selector count though you can use something like un-css to clean up any unused classes.
Documentation. Definitely needs more documentation.
How much css do websites serve up to users?
ESPN 322K Kickstarter 844K Salesforce 1.02M Macaw 593K Adobe 503K Apple Store 440K
The MIT License (MIT)
Copyright (c) 2015 @mrmrs
Permission is hereby granted, free of charge, to any person obtaining a copy
of this software and associated documentation files (the
Software), to deal
in the Software without restriction, including without limitation the rights
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
copies of the Software, and to permit persons to whom the Software is
furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED
AS IS, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN