[Pkg-javascript-devel] Work needed
Xavier
yadd at debian.org
Sun Oct 11 06:27:26 BST 2020
Le 10/10/2020 à 13:35, Jérémy Lal a écrit :
>
>
> Le sam. 10 oct. 2020 à 10:52, Xavier <yadd at debian.org
> <mailto:yadd at debian.org>> a écrit :
>
> Le 27/08/2020 à 12:39, Xavier a écrit :
> > Hi,
> >
> > to prepare bullseye release, we have (at least) to fix:
> > * node-request* removal (replacement by node-got, node-axios,...),
> > needs to fix:
> > - less.js
> > - node-coveralls
> > - node-gyp
> > - node-jsdom
> > - node-jsonld
> > - node-matrix-js-sdk
> > - node-millstone
> > - node-telegram-bot-api
> > - node-yarnpkg
> > * node-cross-spawn removal, only node-execa needs a fix (see
> #959786).
> > Embedding cross-spawn in node-execa could be a solution since
> > vulnerable features seem not used in it
> > * eyes.js: needs a vows update (not released by upstream) #961507
> > * node-xterm: problem with @types/jsdom
> > * nodejs: ppc64el regression #968681
> > * libjs-jquery-hotkeys: jquery.hotkeys changes break python-coverage
> > html reports (#740893)
> >
> > Updating node-jest (not usable for now, migration blocked) should be a
> > good thing but this requires at least node-jsdom fixes.
> >
> > Feel free to update this list of course.
>
> Hi,
>
> I need some help:
> * gyp should be given to Python Team and fixed (#963320)
>
>
> I'll look into fixing it and moving it to Python Team.
>
>
>
> * node-execa/node-cross-spawn: need analysis to see if cross-spawn can
> be safely embedded
>
>
> Can you push upstream tags, please ?
Done, thanks!
More information about the Pkg-javascript-devel
mailing list