Re: On merging the npm importer

2017-03-30 Thread Jan Nieuwenhuizen
Jelle Licht writes: Hi Jelle! > As one of these people living in the "real world", this is exactly how > I have been using the importer up till now. I like and agree with > most of your changes as they make the code much more robust in the > face of inevitable failure. Great! > Nonetheless, on

Re: On merging the npm importer

2017-03-30 Thread Ludovic Courtès
Hello! Christopher Allan Webber skribis: > Jan Nieuwenhuizen writes: [...] >> We have a working importer for npm packages written by Jelle that I have >> been using for about half a year. It can use some improvements and >> that's why I think we should merge it. >> >> Have alook at my npm bra

Re: On merging the npm importer

2017-03-30 Thread Jelle Licht
2017-03-29 19:39 GMT+02:00 Christopher Allan Webber : > Jan Nieuwenhuizen writes: > > > Hi, > > Hi Jan! > Hello Jan and Christopher! > > > We have a working importer for npm packages written by Jelle that I have > > been using for about half a year. It can use some improvements and > > that's

Re: On merging the npm importer

2017-03-29 Thread Christopher Allan Webber
Jan Nieuwenhuizen writes: > Hi, Hi Jan! > We have a working importer for npm packages written by Jelle that I have > been using for about half a year. It can use some improvements and > that's why I think we should merge it. > > Have alook at my npm branch here, rebased on master > > https:

On merging the npm importer

2017-03-28 Thread Jan Nieuwenhuizen
Hi, We have a working importer for npm packages written by Jelle that I have been using for about half a year. It can use some improvements and that's why I think we should merge it. Have alook at my npm branch here, rebased on master https://gitlab.com/janneke/guix I added a patch with se