On Mon, 31 Aug 2026, Thorsten Glaser wrote: >On Mon, 31 Aug 2026, Santiago Vila wrote: > >>During a rebuild of all packages in unstable, this package failed to build.
>Might be to just add node-babel-plugin-add-module-exports to B-D… Turns out to be a bit more. For one: | Error: [BABEL] | /tmp/buildd/dygraphs-2.2.2/disttmp/auto_tests/data/data.js: | @babel/preset-env: The 'bugfixes' option has been removed, and now | bugfix plugins are always enabled. Please remove it from your config. | (While processing: "/usr/share/nodejs/@babel/preset-env/lib/index.js") That is easy enough to work around (check babeljs version, use one config for ≤7 and another for ≥8) but then I get this from browserify: | SyntaxError: 'import' and 'export' may appear only with 'sourceType: | module' (57:0) while parsing | /tmp/buildd/dygraphs-2.2.2/disttmp/src/dygraph.js while parsing file: | /tmp/buildd/dygraphs-2.2.2/disttmp/src/dygraph.js But in contrast to the last successful build in sid, the browserify version has not changed, so node-babel7 8.x has broken more things. Does anyone from its maintainers team know what? Mid-term, the fix will be to convert the JS once, clean it up manually to avoid the extra corner cases handled by the babelified code (the code pretty much is pre-ES6 already with a few exceptions, const, let, and import), but that needs more time and more JS knowledge than I have. Frustrated (the last babeljs update also broke things), //mirabilos -- https://toot.mirbsd.org/@mirabilos/statuses/01KNQD9RNZM1Z2A61AZHG857MP ↑ long list of references on why “AI”/LLMs are bad for everyone also: ↓ from https://toot.cat/@dthompson/117180306961006760 > "responsible LLM usage" is the "clean coal" of the tech world
