Because I think mineral names are cool
- Purely Functional - This was a main focus for the project. I wanted it to be an easy to use, functional system while also being completely pure by making use of piping and transducers to boost performance.
- Single type utility functions - Theoretically, all of the functionality is based around accepting a single data type, doing what it does, and giving you back a result, thus making it reliable, stable, and lightweight.
- Everything is curried! Setup static in one spot and then pass the rest of the dynamic data in later.
- Data last ideology
With a CDN
<!-- It is recommended to replace the @latest with a strict version number for production --><!-- To use the debug friendly kyanite simply remove .min from the filename -->
Or installing with
npm i kyanite and then:
Standard module system
// This will use the module path in the package.json (src/index.js)// However if you want to grab the dev version
// For the prod minified versionconst K =// For the dev/debug friendly versionconst K =
Local copy script tag
<!-- To use the prod minified version --><!-- To use the dev/debug friendly version -->
To run the tests:
git clonethe repo
cdinto the repo folder
A lot of the if not most of the inspiration for this library came from 2 libraries I follow closely, Primarily most of it stems from: