[Pkg-javascript-devel] Advice on packaging a terminal application that uses yarn and webpack

[Jérémy Lal]

On Wed, Apr 13, 2022 at 6:32 PM Julian Gilbey <julian at d-and-j.net> wrote:
>
> Hello,
>
> I was looking into packaging spyder-terminal, a plugin for Spyder (a
> Python IDE) that provides a shell terminal.  But it turns out that far
> from being a Python application, it is essentially a wrapper around a
> Javascript application!  I have had a quick look at the Debian
> archive, wonder how much work would be required to package this.  Here
> are the relevant commands to install the Javascript:
>
> yarn install
> npm i -D webpack
> npm i webpack-cli html-webpack-plugin xterm xterm-addon-attach \
>   xterm-addon-search xterm-addon-web-links xterm-addon-fit
> npm run webpack
>
> Looking through the archive, I see that we have a webpack package
> (which presumably provides the node webpack-cli package).  We also
> have node-xterm, but we don't appear to have html-webpack-plugin or
> any of the four xterm-addon-* packages listed.
>
> I'm also terrified that yarn.lock lists about 730 packages....
>
> What would be needed to package spyder-terminal, then?
>
> Any advice most gratefully received!

Ignore package-lock.json
Check package.json dependencies and devDependencies.

Good news ! They are all in Debian already !
(besides promise-polyfill which is obsolete and should be patched away).

Bad news :( xterm.js debian package needs help.

Also there are tools to help the process of debianizing: npm2deb,
dh-make-node.
They are not perfect, but they can create some default debian/ dir.

Jérémy
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://alioth-lists.debian.net/pipermail/pkg-javascript-devel/attachments/20220413/1420d9c8/attachment.htm>