Your message dated Thu, 24 Feb 2022 17:32:11 +0100
with message-id <[email protected]>
and subject line Re: [Pkg-javascript-devel] Bug#1006378: Bug#1006378:
pkg-js-tools: pkg-js-autopkgtest-require fails with type=module without default
export
has caused the Debian Bug report #1006378,
regarding pkg-js-tools: pkg-js-autopkgtest-require fails with type=module
without default export
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 [email protected]
immediately.)
--
1006378: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1006378
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: pkg-js-tools
Version: 0.12.9
Severity: important
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
EcmaScript modules are supported since nodejs v12.20.0, as documented at
https://nodejs.org/api/esm.html#modules-ecmascript-modules (in the
"History" foldout).
EcmaScript modules can export functions in two ways, and only in one of
them will a default export exists:
https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Statements/export#description
When pkg-js-tools detects that a Node.js library is an EcmaScript module
it runs a test with the assumption that a default export exists.
This fails for EcmaScript modules using named export.
An example is the module espree.
Upgrading Debian package node-espree requires _avoiding_ pkg-js-tools,
because the autopkgtest will fail and apparently cannot be overridden
(seems only additionally added tests can be overridden).
Setting severity=important due to the affect of upgradability of
existing packages.
- Jonas
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAmIXqXYACgkQLHwxRsGg
ASFn4Q//RXdtPNjpWsoyFPLuselxRWi+t2jgNWu+0fTQpMCrOTuyF0ftZg8hyUPe
boLD60GZgwRNtFbJ7+V9RJc5owve0wyOBP4EuCsVauJ4Np4EvDkAIuO2V8F6WFAv
2Z3e8eTZrXZaP1DWaY9b3zWTFoQPRabayH0avaqp1bV6CDr3i/2iITmvpgX8cQi+
vTFwHVSac8P+c7FzvhAXlN9juad7f0i78W36qLdd0ZjLJUZ1clJcV2TekzZqHIgf
dwCWlA539XGLa+ihRVtiybysMJIUqdMyCgkjAbOHhS4bG0kMpqh67GL568FVEzec
YBDyYw8ALaj7IaWw/P0pSaJ9aAk3Ett8cU5c3I148I4I1VdMNWxy1AYiiu8pPvYm
3/gBmltLcYT5Iq2ZfMs7BcpYX+HOCxkA3zmWr4NRCzFgy437e/7iPkjc+deIMkKg
YVRhii36rM/NRPg92iQtV11JlFXohdvKMd7B7uMWu9WgL+YzBHM3pehsYgplACJq
KrZThFIT2Txz0Cya6fqZnmSva94zgTzAAxHjpZWF4Zbh/15z+S4b6Xymi+gW4ylx
p3pGY0vwYy8coujY1UjJ5IW6+pVNGq923rAgU7jG0k/D3YJ8D6eH+k4L6LUWA4hI
ObAud0jCeg/50Xask0Fw40V8MzrpBuTa2w1Mo8/+KxuD5i/mcDs=
=Gz+t
-----END PGP SIGNATURE-----
--- End Message ---
--- Begin Message ---
Quoting Yadd (2022-02-24 17:24:40)
> logically, pkg-js-autopkgtest should ignore such error. Could you give
> me an example ? Current node-espree isn't a module and with next one
> (9.3.1), test passed _(even if it reports an IGNORED error)_ Note:
> reporting such error means that module was loaded, then
> pkg-js-autopkgtest considers that enough to mark test as "PASS
> (superficial)"
Oh, then I must have confused multiple errors - the others I solved or
worked around, but this this one I failed to notice that it was just
noise.
Closing - thanks for the explanation!
- Jonas
--
* Jonas Smedegaard - idealist & Internet-arkitekt
* Tlf.: +45 40843136 Website: http://dr.jones.dk/
[x] quote me freely [ ] ask before reusing [ ] keep private
signature.asc
Description: signature
--- End Message ---
--
Pkg-javascript-devel mailing list
[email protected]
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel
