[Pkg-javascript-devel] Bug#973983: Bug#973983: pkg-js-tools tries to require a non-existing name

[Xavier]

Le 08/11/2020 à 20:52, Julien Puydt a écrit :
> Le dimanche 08 novembre 2020 à 19:07 +0100, Xavier a écrit :
>> Le 08/11/2020 à 18:53, Julien Puydt a écrit :
>>> Le dimanche 08 novembre 2020 à 16:25 +0100, Xavier a écrit :
>>>> did you try to set onne of them in debian/nodejs/main ?
>>>
>>> Oh, dear... putting one of them in there did make things go
>>> through,
>>> but checking the resulting package : all the other components ended
>>> up
>>> in a node_modules directory within the chosen one's directory!
>>>
>>> That's definitely not correct.
>>
>> $ echo '*' > debian/nodejs/root_modules
> 
> The package builds, with just:
> 
> W: node-lumino: nodejs-module-not-declared node-lumino-datastore 
> usr/share/nodejs/@lumino/datastore/package.json
> 
> The inspection of the output of dpkg-deb -c doesn't show anything
> surprising.
> 
> Running through autopkgtest works.
> 
> I'm uploading the result ; the repo is now here:
>   Vcs-Git: https://salsa.debian.org/js-team/lumino.git
>   Vcs-Browser: https://salsa.debian.org/js-team/lumino

Hi,

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). I can update pkg-js-tools to export this name
when package name differs (like mocha, jest, rollup,...).

Cheers,
Xavier