Create a unique string

unique-string-id.js

const uid = () => {
  return Date.now().toString(36) + Math.random().toString(36).substr(2);
};

// Usage. Example, id = khhry2hb7uip12rj2iu
const id = uid();

Better:

const uid = () => Date.now().toString(36) + Math.random().toString(36).substr(2);

how about using performance.now() instead of Date.now()? It should reduce the probability of collision further.

Better:

const uid = () => Date.now().toString(36) + Math.random().toString(36).substr(2);

That's a matter of preference, but yeah 😊

how about using performance.now() instead of Date.now()? It should reduce the probability of collision further.

Even if you're creating thousands of IDs every second, the likelihood of collision is ridiculously low here 😅
But technically speaking, I guess you're right, yeah!

Math.random() can behave deterministically: https://www.tomanthony.co.uk/blog/googlebot-javascript-random/
Prefer Crypto API

Math.random() can behave deterministically: https://www.tomanthony.co.uk/blog/googlebot-javascript-random/
Prefer Crypto API

Absolutely. This is well-known.
That's why it is combined with Date.now().

Let me also just state that this is great for smaller lists and for quickly generating temporary unique strings.
It shouldn't be used for more serious cases, where collisions should be taken into account.
In those cases, use uuid4 instead.

I'm still not sure if I like or dislike that the IDs' alphabetical sort order is also the order by creation time...

You guys sure know about this one? https://gist.github.com/jed/982883

You guys sure know about this one? https://gist.github.com/jed/982883

Sure, but this here is still nice for smaller use cases and 87% faster on my machine: https://jsbench.me/ovkhvq1uct/1

how about using performance.now() instead of Date.now()? It should reduce the probability of collision further.

It will only work on the web, not under Nodejs

Seriously...

https://www.npmjs.com/package/uuid

import { v4 as uuidv4 } from 'uuid';

const myKey = uuidv4();