Consider replacing the dependency on hyperid with native crypto module

[mdstaff]

Feature Request

A single module hyperid imports the base library uuid for generating Ids. This is now supported by default since nodejs 14.17 using the "crypto" module and the "randomUUID" method.

NodeJS 14.X docs about randomUUID: https://nodejs.org/docs/latest-v14.x/api/crypto.html#crypto_crypto_randomuuid_options

Desired Behavior

Remove external dependencies in favor of native nodejs uuid generation

Motivation

Simplicity and reduced asset sizes

Implementation

Replace body of /src/uitilities/createUid.ts with the following:

import { randomUUID } from 'crypto';

export const createUid = (): string => {
  return randomUUID();
};

I can open a PR if that would be helpful.

[gajus]

I think the historical reason for not using crypto was performance.

crypto.randomUUID x 17,421,022 ops/sec ±1.05% (92 runs sampled)
crypto.random x 313,547 ops/sec ±2.88% (82 runs sampled)
hyperid - fixed length, url safe x 20,158,778 ops/sec ±0.54% (94 runs sampled)

However, it looks like randomUUID is comparable in terms of performance.

I cannot think of any reason not to add this change.

[github-actions]

🎉 This issue has been resolved in version 33.0.9 🎉

The release is available on:

• GitHub release
• npm package (@latest dist-tag)

Your semantic-release bot 📦🚀