node-rjsf builds esm/cjs bundles,
and depends on node-nanoid.
node-nanoid correctly exports a browser bundle,
but node-rjsf doesn't use that file, it uses the cjs file,
which require "node:crypto": that's really bad, because
the nanoid/index.browser.js file instead use native window.crypto.getRandomValues,
and they are not interchangeable.
This produces bugs when a project makes a bundle with @rjsf/core in it,
webpack will complain about node: prefix not supported,
but problem isn't in webpack at all, it's really a problem with rjsf.