Package: node-rjsf Version: 5.12.1+~5.0.1-3 Severity: important 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. -- System Information: Debian Release: forky/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 6.12.38+deb13-amd64 (SMP w/4 CPU threads; PREEMPT) Locale: LANG=fr_FR.utf8, LC_CTYPE=fr_FR.utf8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages node-rjsf depends on: ii node-ajv 8.12.0~ds+~2.1.1-5 ii node-lodash 4.17.21+dfsg+~cs8.31.198.20210220-9 ii node-markdown-to-jsx 7.2.0+dfsg-3 ii node-postcss [node-nanoid] 8.5.6+~cs9.3.28-1 ii node-prop-types 15.8.1+~15.7.9+~cs1.1.1-1 node-rjsf recommends no packages. node-rjsf suggests no packages. -- no debconf information -- Pkg-javascript-devel mailing list Pkg-javascript-devel@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel
