Drop external uuid dependency in favor of native functionality

[vhscom]

Describe the problem

The default demo currently uses a dev dependency for generating random v4 UUIDs inside the hooks file which has been available natively in Node and the Web Crypto API for some time now. In Node crypto.randomUUID() it has been available since v14.17.0. The Web Cryptography API, which appears to support web workers as well, uses the same method name.

Describe the proposed solution

Dropping this dependency now that support for Node 14 has ended seems like a good time to cut the baggage.

Alternatives considered

Leave the dependency in place. It's slower than native methods but probably not noticeable in the demo.

Importance

nice to have

Additional Information

No response

[Conduitry]

What happens when the app is deployed with an adapter to an environment that doesn't have the Node runtime available?

[ghostdevv]

Also luke's uuid package isn't exactly slow:

• https://github.com/lukeed/uuid#benchmarks
• https://github.com/lukeed/uuid#performance

[jrmoynihan]

Nanoid is even smaller and faster, if I recall correctly.

[paperdave]

ive been looking at a few issues, and i think this change should definitely be done after #4934 is merged, since it seems to include the web crypto global, where the example can use the web crypto method.

[vhscom]

What happens when the app is deployed with an adapter to an environment that doesn't have the Node runtime available?

Thanks. I tried a Pages build after I saw your comment and your intuition was right. The build fails with a reference error as crypto import can't be used in the worker as, in the worker context, it's a global. And we can't currently remove the import in the hooks file (despite valid syntax) as crypto isn't available in the global namespace during the kit build.

[paperdave]

Thanks. I tried a Pages build after I saw your comment and your intuition was right. The build fails with a reference error as crypto import can't be used in the worker as, in the worker context, it's a global. And we can't currently remove the import in the hooks file (despite valid syntax) as crypto isn't available in the global namespace during the kit build.

this is an issue i currently face on my own site, but i have this hack in my svelte config

import { webcrypto } from 'crypto';
global.crypto = webcrypto;

(this works because the config is run only in node environments, and during dev and build its all sharing that global scope)

we obviously shouldn't throw this in the demo, but it's fine as a temp fix for other projects.