nodejs August 2019

nodejs@lists.fedoraproject.org

2 participants
3 discussions

Re: Updating nodejs-grunt and friends in Rawhide
by Tom Hughes 24 Sep '19

24 Sep '19

On 29/08/2019 20:01, Ben Rosser wrote: > Hm, does it make sense then to have a compatibility package for lodash3? I think we may have to multiversion it yes. Been thinking that for a while. I'll try and have a look at doing a lodash4 version of the spec over the weekend... > dnf repoquery --whatrequires nodejs-lodash says: You need to look at all the nodejs-lodash-xxx modules as well which are built from the same source, although they don't make as much difference as I expected. That and BRs which I haven't looked at. > My guess is also that at least *some* of these packages have a newer > release which support lodash 4 but no one has updated the package, > whether because the package is effectively unmaintained or the > maintainer is overworked or worried about breaking dependencies. :( Oh probably quite a lot do, it's been a bit chicken and egg having to try and do everything at once, or even audit what is actually doable - ie what dependants have a new version with support. > For instance, looking at the last package on this list... the current > version of zip-stream is 2.1.2 and does not actually require lodash at > all anymore. > > https://github.com/archiverjs/node-zip-stream/blob/master/package.json Somebody should update it then ;-) Tom -- Tom Hughes (tom(a)compton.nu) http://compton.nu/

2 5

Fwd: Updating nodejs-grunt and friends in Rawhide
by Ben Rosser 29 Aug '19

29 Aug '19

(My bad, I didn't notice I had to manually reply all on this list. Apologies) On Thu, Aug 29, 2019 at 2:44 PM Tom Hughes <tom(a)compton.nu> wrote: > > On 29/08/2019 14:37, Ben Rosser wrote: > > > I can work on this and submit pull requests to the packages in > > question, if that would be helpful, but I wanted to check in here > > before doing so. As best as I can tell, the packages in question that > > need updating are: > > > > * nodejs-grunt > > * nodejs-grunt-legacy-log > > * nodejs-grunt-legacy-log-util > > Both legacy-log and legacy-log-util are mine and the reason > that I haven't updated them is that the 2.x versions require > lodash 4.x and we don't have that and getting to it is a major > project because 3.x and 4.x are totally incompatible and lots > of things use it. Plus lodash has a crazy system that packages > the same code is lots of different variants. > > Tom > > -- > Tom Hughes (tom(a)compton.nu) > http://compton.nu/ Hm, does it make sense then to have a compatibility package for lodash3? dnf repoquery --whatrequires nodejs-lodash says: discord-irc-0:2.6.1-3.fc30.noarch nodejs-archiver-0:1.0.1-5.fc29.noarch nodejs-archiver-utils-0:1.3.0-8.fc30.noarch nodejs-benchmark-0:2.0.0-7.fc30.noarch nodejs-cheerio-0:0.20.0-4.fc30.noarch nodejs-coffee-coverage-0:2.0.1-5.fc30.noarch nodejs-conventional-changelog-core-0:2.0.11-2.fc29.noarch nodejs-conventional-changelog-writer-0:3.0.9-3.fc30.noarch nodejs-conventional-commits-parser-0:2.1.7-4.fc30.noarch nodejs-fg-lodash-0:0.0.2-8.fc30.noarch nodejs-glob-expand-0:0.2.1-4.fc30.noarch nodejs-globule-0:0.2.0-11.fc30.noarch nodejs-grunt-contrib-csslint-0:0.4.0-12.fc30.noarch nodejs-grunt-contrib-less-0:1.2.0-6.fc30.noarch nodejs-grunt-contrib-uglify-0:0.11.1-10.fc30.noarch nodejs-grunt-contrib-watch-0:0.6.1-12.fc30.noarch nodejs-grunt-init-0:0.3.2-9.fc30.noarch nodejs-grunt-legacy-log-0:1.0.2-3.fc30.noarch nodejs-grunt-legacy-log-utils-0:1.0.0-7.fc30.noarch nodejs-grunt-legacy-util-0:1.0.0-6.fc29.noarch nodejs-grunt-saucelabs-0:8.6.1-11.fc30.noarch nodejs-i18n-transform-0:2.1.3-7.fc30.noarch nodejs-markdown-it-testgen-0:0.1.4-7.fc30.noarch nodejs-std-mocks-0:1.0.0-8.fc30.noarch nodejs-tap-spec-0:4.1.1-4.fc30.noarch nodejs-xmlbuilder-0:4.2.1-7.fc30.noarch nodejs-zip-stream-0:0.7.0-9.fc30.noarch I own discord-irc, and I happen to know it actually wants lodash 4 but seems to (mostly) work with the version of lodash is in Fedora 30-- I'm running an instance of it currently on a F30 machine. See upstream's package.json here: https://github.com/reactiflux/discord-irc/blob/v2.6.1/package.json#L45 My guess is also that at least *some* of these packages have a newer release which support lodash 4 but no one has updated the package, whether because the package is effectively unmaintained or the maintainer is overworked or worried about breaking dependencies. :( For instance, looking at the last package on this list... the current version of zip-stream is 2.1.2 and does not actually require lodash at all anymore. https://github.com/archiverjs/node-zip-stream/blob/master/package.json Ben Rosser

1 0

Updating nodejs-grunt and friends in Rawhide
by Ben Rosser 29 Aug '19

29 Aug '19

Hello, Over the last few days, I took over some pieces of nodejs-grunt that had been retired due to being FTBFS in F31/Rawhide: * nodejs-grunt-legacy-util * nodejs-grunt-contrib-nodeunit * nodeunit * nodejs-dateformat (not part of grunt, but a dependency) Without grunt-legacy-util, as far as I can tell, nodejs-grunt was unusable-- a package I had that used grunt for its unit tests could not be built because grunt could not be installed. So things were unfortunately pretty broken here. I've updated all four packages to their latest upstream releases and rebuilt them successfully. However, the-- outdated-- version of grunt we are shipping explicitly requires grunt-legacy-util >= 1.0 && < 1.1. grunt-legacy-util in Rawhide is now version 1.1, so to finish this we either need to update the rest of grunt (or use %nodejs_fixdep and hope for the best, I suppose). I can work on this and submit pull requests to the packages in question, if that would be helpful, but I wanted to check in here before doing so. As best as I can tell, the packages in question that need updating are: * nodejs-grunt * nodejs-grunt-legacy-log * nodejs-grunt-legacy-log-util Cheers, Ben Rosser

2 1

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

nodejs August 2019