Package: rollup Version: 3.29.5-1 Severity: normal It seems that rollup emits `Object.prototype.__proto__`, which is a problem because we decided to --disable-proto when running pkgjs autopkgtests.
Example: node-prosemirror-view https://ci.debian.net/packages/n/node-prosemirror-view/unstable/amd64/54772640/ Upstream rollup seems to be aware of it, but is ignoring the issue: https://github.com/rollup/rollup/issues/3140 However their discussion was around __proto__, and did not make a distinction between the two uses of it (one okay, one bad), so I tried to revive that issue. Meanwhile, maybe we could either: - patch rollup - just use esbuild to build things... - not use --disable-proto when the package build-depends on rollup Jérémy -- System Information: Debian Release: trixie/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 6.12.9-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 rollup depends on: ii nodejs 22.12.0+dfsg-3 rollup recommends no packages. Versions of packages rollup suggests: ii node-chokidar 3.6.0-2 -- no debconf information
