Package Exports

book-of-spells
book-of-spells/index.mjs

This package does not declare an exports field, so the exports above have been automatically detected and optimized by JSPM instead. If any package subpath is missing, it is recommended to post an issue to the original package (book-of-spells) to support the "exports" field. If that is not possible, create a JSPM override to customize the exports field for this package.

Readme

📖 Stamat's Book of JavaScript Spells

A collection of JavaScript functions and snippets that I use in my projects in ESM format. This is mainly for my own reference, but I hope it can be useful to others as well.

The problem, Bernard, is that what you and I do is so complicated. We practice witchcraft. We speak the right words. Then we create life itself… out of chaos. - Dr. Robert Ford, Westworld S01E02

Installation

npm i book-of-spells

Usage

📖 Documentation

  import { clone } from 'book-of-spells' // if your bundler doesn't resolve npm packages use the full path: import { clone } from './node_modules/book-of-spells/index.mjs'

  const a = { a: 1, b: 2, c: { d: 3, e: 4} }
  const b = clone(a)

  console.log( a.c === b.c ) // false

Why

After 14+ years of JavaScript and copy-pasting my own undocumented code, I've decided to start documenting it. I'm not sure why I didn't do it sooner. Actually, I'm lying, I do know why. I am so lazy that I'd rather copy or write the same code over and over again than document it - which is, of course, much more work than keeping and maintaining it in one place and distributing it as a package.

It's not only laziness, if you think about it. It is this omnipresent fear of change, of the unknown, of the new. But change is good. Being unconformable is good. It means you're growing. It means you're learning. It means you're alive.

Contributing

If you have a function or a snippet that you think is useful, please open a PR. I'd love to see what you've got.

With love 💖, Stamat