More meaningful name for `invariant` function

I would like to have a more meaningful name for the function than invariant. Something like throwOnFalsy is for me easier to understand.

While working with developers that don’t know what tiny-invariant is, I realized that is not easy understand at first sight what the invariant function does. To improve this, it would be nice to rename the function with something more descriptive. I would still keep the original function to avoid breaking changes but also allow to import the new function with the descriptive name.

What do you think? Is throwOnFalsy good for you or maybe you have a better name? If you think it is a good idea, I would submit a PR for that.

[alexreardon]

I agree entirely that invariant is not a great name. Personally, I think assert would be a way clearer name than invariant. However, leaning on invariant means that tooling that automatically allows invariant messages to be stripped (eg https://www.npmjs.com/package/babel-plugin-dev-expression) just works™️

Personally, I would like to see us move away from invariant towards assert. I am exploring making a new (ESM only) assert package: https://github.com/alexreardon/tiny-assert

[pkerschbaum]

I guess this package tiny-invariant could just re-export the default function as a named export assert.
So that people could do:

import { assert } from 'tiny-invariant';

Autosuggestion and autoimport of IDEs (e.g. VS Code) would probably benefit from that.