Fix: Use nanonid/non-secure instead of cuid

[bharatkashyap]

• Closes Update cuid to paralleldrive/cuid2 #1737

[Janpot]

👍 We can start with this, it will take care of the yarn warning.

In direction 13 mode cuid is probably overkill for what we use it for. Most usage we can probably replace with simpler methods:

• nodeId: we can probably replace by an id based on an incrementing integer, these don't benefit anymore from being globally unique. In fact they are regenerated every time the dom is loaded from disk
• page file id: we can probably replace by a name generator. Could be more user friendly as well, until we decide to change the routing to be file name based
• monaco editor, we can probably also replace it by an id based on an integer.

For later though!

[bharatkashyap]

@Janpot https://app.circleci.com/pipelines/github/mui/mui-toolpad/6991/workflows/e354df79-c205-4539-a273-61fc4dfb4023/jobs/30387 Is it apparent to you why this test is failing - I can't see why this fails

[Janpot]

Does it pass locally?

[bharatkashyap]

Does it pass locally?

No, fails with the same mysterious stack trace

[Janpot]

cuid2 API seems to be designed to init only once.

import { init } from '@paralleldrive/cuid2';

const createIdInternal = init({ length: 7 })

export function createId(): NodeId {
  return createIdInternal() as NodeId;
}

[bharatkashyap]

This still fails on yarn test with the same error as in the CI

[Janpot]

yes, I wasn't proposing this as a fix for that, just as a suggestion to use the lib in a more idiomatic way.

Let's just move to nanoid/non-secure instead of cuid2. That's more than suitable for our needs and won't have these issues

[Janpot]

Suggested change

	id: cuid2({ length: appDom.SLUG_LENGTH })(),
	id: appDom.createId(),