Your message dated Mon, 09 Nov 2020 07:59:06 +0100 with message-id <273117e56f6342127003fec4118b9205b0a49fef.ca...@gmail.com> and subject line Re: [Pkg-javascript-devel] Bug#973983: pkg-js-tools tries to require a non-existing name has caused the Debian Bug report #973983, regarding pkg-js-tools should export main name when package name differs to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 973983: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=973983 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
--- Begin Message ---Package: pkg-js-tools Version: 0.9.45 I'm trying to package lumino (ITP 972487), which has a pretty special structure: - no main module ; - only packages. My d/control has a build dep on pkg-js-tools, and uses "Provides: ${nodejs:Provides}" ; I have a d/nodejs/additional_components with packages/* to find the packages and my d/tests/pkg-js/test is only an "echo FIXME". When building the package, I get strange warnings, but they seem pretty harmless : dh_auto_install: warning: # /! "types" field should be replaced by "typings" in packages/algorithm/package.json Please report this bug Things get bad when autopkgtest kicks in and tries to require: autopkgtest [15:44:43]: test pkg-js-autopkgtest-require: [------------- ---------- Using package.json Node module name is Test: require internal/modules/cjs/loader.js:898 throw new ERR_INVALID_ARG_VALUE('id', id, ^ TypeError [ERR_INVALID_ARG_VALUE]: The argument 'id' must be a non- empty string. Received '' at Module.require (internal/modules/cjs/loader.js:898:11) at require (internal/modules/cjs/helpers.js:74:18) at [eval]:1:1 at Script.runInThisContext (vm.js:120:18) at Object.runInThisContext (vm.js:309:38) at Object.<anonymous> ([eval]-wrapper:10:26) at Module._compile (internal/modules/cjs/loader.js:1015:30) at evalScript (internal/process/execution.js:94:25) at internal/main/eval_string.js:23:3 { code: 'ERR_INVALID_ARG_VALUE' } indeed, the main package.json has no 'name' field. It should instead try to require the packages listed in d/nodejs/additional_components. Is it possible to get around it? Cheers, JP
--- End Message ---
--- Begin Message ---Hi, Le dimanche 08 novembre 2020 à 21:45 +0100, Xavier a écrit : > no bug here, pkg-js-tools never export "main" component since it's > normally the package name. You just have to export it by hand in > debian/control (done). Thanks. > I can update pkg-js-tools to export this name > when package name differs (like mocha, jest, rollup,...). Yes, I think it would make sense. Closing that bug now that the situation is handled. Thanks! JP
--- End Message ---
-- Pkg-javascript-devel mailing list Pkg-javascript-devel@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel
