Source: node-rollup-plugin-inject Version: 4.0.2+~3.0.2-1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20211023 ftbfs-bookworm
Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[1]: Entering directory '/<<PKGBUILDDIR>>' > dh_auto_build --buildsystem=nodejs > Found debian/nodejs/legacy/build > cd ./legacy && sh -ex ../debian/nodejs/legacy/build > + rollup -c > > src/index.js → dist/rollup-plugin-inject.cjs.js, > dist/rollup-plugin-inject.es6.js... > (!) Entry module "src/index.js" is implicitly using "default" export mode, > which means for CommonJS output that its default export is assigned to > "module.exports". For many tools, such CommonJS output will not be > interchangeable with the original ES module. If this is intended, explicitly > set "output.exports" to either "auto" or "default", otherwise you might want > to consider changing the signature of "src/index.js" to use named exports > only. > https://rollupjs.org/guide/en/#outputexports > src/index.js > created dist/rollup-plugin-inject.cjs.js, dist/rollup-plugin-inject.es6.js in > 51ms > cd packages/inject && rollup -c > > src/index.js → dist/index.js, dist/index.es.js... > (!) Entry module "src/index.js" is implicitly using "default" export mode, > which means for CommonJS output that its default export is assigned to > "module.exports". For many tools, such CommonJS output will not be > interchangeable with the original ES module. If this is intended, explicitly > set "output.exports" to either "auto" or "default", otherwise you might want > to consider changing the signature of "src/index.js" to use named exports > only. > https://rollupjs.org/guide/en/#outputexports > src/index.js > created dist/index.js, dist/index.es.js in 90ms > make[1]: Leaving directory '/<<PKGBUILDDIR>>' > dh_auto_test --buildsystem=nodejs > mkdir -p node_modules/\@rollup > ln -s ../../packages/inject node_modules/\@rollup/plugin-inject > cd ./legacy && sh -ex ../debian/nodejs/legacy/test > + mocha -R spec > > > rollup-plugin-inject > undefined inserts a default import statement > undefined uses the modules property > 1) inserts a named import statement > undefined overwrites keypaths > undefined ignores existing imports > undefined handles shadowed variables > 2) handles shorthand properties > undefined handles redundant keys > 3) generates * imports > rollup-plugin-inject: failed to parse > /<<PKGBUILDDIR>>/legacy/test/samples/non-js/styles.css. Consider restricting > the plugin to particular files via options.include > undefined transpiles non-JS files but handles failures to parse > > > 7 passing (98ms) > 3 failing > > 1) rollup-plugin-inject > inserts a named import statement: > > AssertionError [ERR_ASSERTION]: import { Promise as Promise$1 } from > 'es6-promise'; > > Promise$1.all([ thisThing, thatThing ]).then( () => someOtherThing ); > > + expected - actual > > -false > +true > > at Context.<anonymous> (test/test.js:50:12) > > 2) rollup-plugin-inject > handles shorthand properties: > > AssertionError [ERR_ASSERTION]: import { Promise as Promise$1 } from > 'es6-promise'; > > const polyfills = { Promise: Promise$1 }; > polyfills.Promise.resolve().then( () => 'it works' ); > > + expected - actual > > -false > +true > > at Context.<anonymous> (test/test.js:106:12) > > 3) rollup-plugin-inject > generates * imports: > > AssertionError [ERR_ASSERTION]: import * as foo from 'foo'; > > console.log( foo.bar ); > console.log( foo.baz ); > > + expected - actual > > -false > +true > > at Context.<anonymous> (test/test.js:138:12) > > > > dh_auto_test: error: cd ./legacy && sh -ex ../debian/nodejs/legacy/test > returned exit code 3 The full build log is available from: http://qa-logs.debian.net/2021/10/23/node-rollup-plugin-inject_4.0.2+~3.0.2-1_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! If you reassign this bug to another package, please marking it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects If you fail to reproduce this, please provide a build log and diff it with mine so that we can identify if something relevant changed in the meantime.
