v2

[tobiasahlin]

This PR puts SpinKit on v2.0.0. It reworks a few of the spinners, adds a new one, removes all dependencies, and moves away from SCSS in favor of using CSS variables for all configurations.

Changelog

• New: Added examples.html, with an overview of all spinners
• New: Added a brand new chase spinner
• New: Added spinkit.min.css
• Fixed: inline-block is no longed used to position any spinners (decoupling spacing from any potential font effects).
• Changed: Most spinners now have more distinct and shorter names.
• Changed: No positioning is now applied by default on any of the spinners.
• Changed: All elements now only have one single class.
• Changed: No more dependencies. gulp, npm, node, etc. is not required to build this project. There's nothing to build.
• Changed: No more SCSS. All configuration is now done through CSS vars.
• Fixed: All keyframe animations are now named after the elements/classes that are using them.

Fixes

• Fixes Conflict with circle and fading circle #141 by using unique classes for all spinners.
• Fixes wave rely on spaces between rects elements #139 by using flexbox rather than inline-block for positioning.
• Fixes Prevent spinner from using custom font faces #137 (same as above)
• Fixes Wandering Cube should use a variable for width/height for scaling/centering #122 by using relative values for all children
• Fixes frame name  #110 by updating http://tobiasahlin.com/spinkit/ to use the latest SpinKit version
• Fixes package.json breaks npm import with Browserify #96 by removing all dependencies

[tobiasahlin]

Preview of new chase spinner:

[wolfika]

Changed: No more dependencies. gulp, npm, node, etc. is not required to build this project. There's nothing to build.

@tobiasahlin You are right in a sense that there's nothing to build as no preprocessors are present anymore, but don't you want to maybe have a very minimalistic npm script (or something) way of generating the minified CSS? I can imageine re-generating this file manually can be tedious.

[tobiasahlin]

@wolfika Possibly, let's evaluate and see 🙏 as long as the build process is literally one single to minimize the CSS (like it is now), I don't think it's too bad. Let's see!