Hi, There is npm2deb. Running `npm2deb depends -b -r <pkg name in npm dot js>` can give you an idea about the dependency tree (the commands might be a bit different, it's been a while since I last dealt with it). Although I have to warn you that it is...... *very slow*.
Best, Ananthu On 7 October 2024 4:21:55 pm UTC, "Antoine Beaupré" <anar...@debian.org> wrote: >Hi! > >I'm part of the golang team (in CC) which is responsible for packaging >the Prometheus package, a golang-based monitoring system. Recently, >upstream switched from a "classic" HTML-based interface to a rather >more... complicated JavaScript frontend built with React. > >We've looked at packaging this in Debian (#1083100, also in CC), and >quickly got worried about the number of dependencies we'd need to >package. > >Do you have advice on how to move forward on this? > >I was wondering if there's some magic command we can run to actually get >a more solid view on the tasks needed? Like a command that would parse >the package.json and report which packages are missing from Debian, >which have WNPP bugs, etc... > >How involved is it to package React stuff? > >How maintainable is it in the long run in Debian? > >Thanks for any advice! > >a. > >-- >The odds are greatly against you being immensely smarter than everyone >else in the field. If your analysis says your terminal velocity is >twice the speed of light, you may have invented warp drive, but the >chances are a lot better that you've screwed up. > - Akin's Laws of Spacecraft Design >
