UID

To generate a stable UID/Key for a given item, consistently between client and server, in 900 bytes.

⚠️ SSR: Not compatible with Strict or Concurent mode. Consider using native useId(React 18) hook instead.

If your clientside is using StrictMode it will never match SSR-ed Ids due to double invocation

Example - https://codesandbox.io/s/kkmwr6vv47

API

React UID provides 3 different APIs

• vanilla js API - uid(item) -> key
• React Component, via renderProp based API - <UID>{ id => <><label htmlFor={id}/><input id={id}/></>}</UID>
• React Hooks - useUID

Javascript

• uid(item, [index]) - generates UID for an object(array, function and so on), result could be used as React key. item should be an object, but could be anything. In case it is not an "object", and might have non-unique value - you have to specify second argument - index

1import { uid } from 'react-uid';
2
3// objects
4const data = [{ a: 1 }, { b: 2 }];
5data.map((item) => <li key={uid(item)}>{item}</li>);
6
7// unique strings
8const data = ['a', 'b'];
9data.map((item) => <li key={uid(item)}>{item}</li>);
10
11// strings
12const data = ['a', 'a'];
13data.map((item, index) => <li key={uid(item, index)}>{item}</li>);

JS API might be NOT (multi-tenant)SSR friendly,

React Components

• (deprecated)UID - renderless container for generation Ids
• UIDConsumer - renderless container for generation Ids

1 import {UID} from 'react-uid';
2
3 <UID>
4     {id => (
5       <Fragment>
6         <input id={id} />
7         <label htmlFor={id} />
8       </Fragment>
9     )}
10 </UID>
11
12 // you can apply some "naming conventions" to the keys
13  <UID name={ id => `unique-${id}` }>
14      {id => (
15        <Fragment>
16          <input id={id} />
17          <label htmlFor={id} />
18        </Fragment>
19      )}
20  </UID>
21
22  // UID also provide `uid` as a second argument
23  <UID>
24       {(_, uid) => (
25         data.map( item => <li key={uid(item)}>{item}</li>)
26       )}
27  </UID>
28
29  // in the case `item` is not an object, but number or string - provide and index
30  <UID>
31       {(_, uid) => (
32         data.map( (item, index) => <li key={uid(item, index)}>{item}</li>)
33       )}
34  </UID>

The difference between uid and UID versions are in "nesting" - any UID used inside another UID would contain "parent prefix" in the result, scoping uid to the local tree branch.

UID might be NOT SSR friendly,

Hooks (16.8+)

• useUID() will generate a "stable" UID
• useUIDSeed() will generate a seed generator, you can use for multiple fields

1import { useUID, useUIDSeed } from 'react-uid';
2
3const Form = () => {
4  const uid = useUID();
5  return (
6    <>
7     <label htmlFor={uid}>Email: </label>
8     <input id={uid} name="email" />
9    </>
10  )
11}
12
13const Form = () => {
14  const seed = useUIDSeed();
15  return (
16    <>
17     <label htmlFor={seed('email')}>Email: </label>
18     <input id={seed('email')} name="email" />
19     {data.map(item => <div key={seed(item)}>...</div>
20    </>
21  )
22}

Hooks API is SSR friendly,

Server-side friendly UID

• UIDReset, UIDConsumer, UIDFork - SSR friendly UID. Could maintain consistency across renders. They are much more complex than UID, and provide functionality you might not need.

The key difference - they are not using global "singlentone" to track used IDs, but read it from Context API, thus works without side effects.

Next example will generate the same code, regardless how many time you will render it

1import { UIDReset, UIDConsumer } from 'react-uid';
2
3<UIDReset>
4  <UIDConsumer>
5    {(id, uid) => (
6      <Fragment>
7        <input id={id} />
8        <label htmlFor={id} />
9        data.map( item => <li key={uid(item)}>{item}</li>)
10      </Fragment>
11    )}
12  </UIDConsumer>
13</UIDReset>;

UID is not 100% SSR friendly - use UIDConsumer.

Code splitting

Codesplitting may affect the order or existence of the components, so alter the componentDidMount order, and change the generated ID as result.

In case of SPA, this is not something you should be bothered about, but for SSR this could be fatal.

Next example will generate consistent keys regardless of component mount order. Each call to UIDFork creates a new branch of UIDs untangled from siblings.

1import {UIDReset, UIDFork, UIDConsumer} from 'react-uid';
2
3 <UIDReset>
4     <UIDFork>
5      <AsyncLoadedCompoent>
6         <UIDConsumer>
7           { uid => <span>{uid} is unique </span>}
8         </UIDConsumer>
9     </UIDFork>
10     <UIDFork>
11       <AsyncLoadedCompoent>
12          <UIDConsumer>
13            { uid => <span>{uid} is unique </span>}
14          </UIDConsumer>
15      </UIDFork>
16 </UIDReset>

The hooks API only needs the <UIDFork> wrapper.

So hard?

"Basic API" is not using Context API to keep realization simple, and React tree more flat.

Types

Written in TypeScript

Licence

MIT