		{
		"name": "@flekschas/utils",
		"version": "0.1.0",
		"version": "0.2.0",
		"description": "A set of utility functions I use across projects",
		@@ -13,8 +13,11 @@ "author": {
		"license": "MIT",
		"main": "umd/index.js",
		"module": "esm/index.js",
		"main": "utils.js",
		"module": "utils.esm.js",
		"unpkg": "utils.min.js",
		"files": [
		"src/*",
		"dist/*"
		"dist"
		],
		"publishConfig": {
		"access": "public"
		},
		"homepage": "https://github.com/flekschas/utils",
		@@ -21,0 +24,0 @@ "repository": {

dist/README.md

		# A collection of handy utility functions

		[![NPM Version](https://img.shields.io/npm/v/@flekschas/utils.svg?style=flat-square&color=7f99ff)](https://npmjs.org/package/@flekschas/utils)
		[![Build Status](https://img.shields.io/travis/flekschas/utils?color=a17fff&style=flat-square)](https://travis-ci.org/flekschas/utils/)
		[![File Size](http://img.badgesize.io/https://unpkg.com/@flekschas/utils/utils.min.js?compression=gzip&style=flat-square&color=e17fff)](https://unpkg.com/@flekschas/utils/utils.min.js)
		[![Code Style Prettier](https://img.shields.io/badge/code%20style-prettier-ff7fe1.svg?style=flat-square)](https://github.com/prettier/prettier#readme)

		This is a collection of utility functions that I keep using across different
		@@ -31,7 +36,12 @@ projects. I primarily created this package for myself so I don't have to

		- animation
		- color
		- conversion
		- dom
		- event
		- functional-programming
		- geometry
		- map
		- numerics
		- math
		- object
		- other
		@@ -42,2 +52,3 @@ - sorting
		- type-checking
		- vector

		@@ -54,7 +65,7 @@ ## Why
		add a function I will make sure it's _performant_. Finally, every function
		should be implement as _simplictic as possible_ without harming performance.
		There's always trade-off between performance and simplicity and my philosophy
		should be implement as _simple as possible_ without harming performance.
		There's always a trade-off between performance and simplicity and my philosophy
		is the following: if the simple and complex implementation perform roughly the
		same I choose the simple implementation. But if a slightly more complex
		implementation is much faster I will favor it. In any case, the API should
		always by simple and easy to understand!
		same, I choose the simple implementation. If a slightly more complex
		implementation is much faster I will favor the complex implementation. In any
		case, the API should always be simple and easy to understand!

package.json

		{
		"name": "@flekschas/utils",
		"private": false,
		"version": "0.1.0",
		"version": "0.2.0",
		"description": "A set of utility functions I use across projects",
		@@ -14,8 +14,11 @@ "author": {
		"license": "MIT",
		"main": "dist/umd/index.js",
		"module": "dist/esm/index.js",
		"main": "dist/utils.js",
		"module": "dist/utils.esm.js",
		"unpkg": "dist/utils.min.js",
		"files": [
		"src/*",
		"dist/*"
		"dist"
		],
		"publishConfig": {
		"access": "public"
		},
		"scripts": {
		@@ -25,3 +28,3 @@ "build": "rm -rf dist/*; rollup -c; node scripts/build.js",
		"precommit": "NODE_ENV=production lint-staged",
		"prepublishOnly": "npm run test",
		"prepublishOnly": "npm run test; npm run build",
		"prerelease": "npm run build; zip -r dist.zip dist",
		@@ -28,0 +31,0 @@ "pretest": "npm run lint",

README.md

		@@ -36,2 +36,3 @@ # A collection of handy utility functions

		- animation
		- color
		@@ -45,2 +46,3 @@ - conversion
		- math
		- object
		- other
		@@ -51,2 +53,3 @@ - sorting
		- type-checking
		- vector

		@@ -53,0 +56,0 @@ ## Why

src/color.js

src/conversion.js

src/dom.js

src/event.js

src/functional-programming.js

src/geometry.js

src/index.js

src/map.js

src/math.js

src/other.js

src/sorting.js

src/string.js

src/timing.js

src/type-checking.js

@flekschas/utils - npm Package Compare versions

New alerts

Fixed alerts

Improved metrics

Worsened metrics