[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: how to deal with source maps (was Re: Typescript definitions in binary packages)



On 8/31/25 09:10, Julian Gilbey wrote:
On Thu, Aug 28, 2025 at 09:33:53PM +0200, Yadd wrote:
On 8/28/25 19:51, Jérémy Lal wrote:
[...]
     Thanks for this analysis.  In node-htmlparser2, for example, we find
     files such as

     /usr/share/nodejs/htmlparser2/lib/Tokenizer.d.ts.map
     /usr/share/nodejs/htmlparser2/lib/Tokenizer.js.map
     /usr/share/nodejs/htmlparser2/lib/esm/Tokenizer.d.ts.map
     /usr/share/nodejs/htmlparser2/lib/esm/Tokenizer.js.map

     These refer to the sources being in ../src or ../../src respectively;
     these are not included in the Debian package.

     I don't have any view on whether we want source maps or even the
     sources in our packages.


Could anyone from the javascript team think about it ?

The upstream package is distributed as this (except that sourcemaps links
points to raw.githubusercontent.com). This bug is fixed in 10.0.0

Thanks Yadd!

There are two other packages showing a similar behaviour:
node-domutils and node-entities.  The errors/warnings are given below
again for reference.  Are these due to similar causes?

Best wishes,

    Julian
Yes, same bug, same upstream


Reply to: