Re: [Pkg-javascript-devel] RFS: node-timeago.js

On വെ, Jan 10, 2020 at 19:12, Sakshi Sangwan wrote: Hello, I've updated the Debian package of node-timeago.js. The package was tested on sbuild and was successfully built. It is also lintian clean. I've pushed the changes to salsa repo which may be found at:

Re: [Pkg-javascript-devel] gulp 4 migration

On 2020, ജനുവരി 11 3:06:24 PM IST, Xavier wrote: >Hi, > >gulp-4 and vinyl-fs seems ready to unstable migration. Can I push them >? Did you try rebuilding reverse build dependencies? Last time when I tried it did not work for any of those like babel 6, postcss etc -- Sent from my Android

Re: [Pkg-javascript-devel] Rollup in Debian

On ഞാ, Jan 5, 2020 at 16:19, Julien Puydt wrote: Hi, upstream is up to 1.28.0 ; Debian unstable has only 0.68.2, experimental has 1.10.1. A number of rollup-plugin-foos need at least version 1 to build, and quite a few of them have been merged into a single repository here :

[Pkg-javascript-devel] Bug#947760: Bug#947760: Bug#947760: why ?

On തി, Dec 30, 2019 at 10:48, Xavier wrote: Hi, See node-es6-iterator debian/tests/control, 'yarnpkg install' fails without npm. You should add npm as recommended dependency at least That is likely a bug in node-es6-iterator or it needs npm explicitly. In gitlab, yarnpkg install has been

Re: [Pkg-javascript-devel] getting nodejs 12 in debian sid

On 2019, ഡിസംബർ 28 12:45:32 AM IST, Utkarsh Gupta wrote: >Hi there, > >On 13/12/19 12:20 pm, Pirate Praveen wrote: >> On 2019, ഡിസംബർ 13 7:50:50 AM IST, "shirish शिरीष" > wrote: >>> Any update as to when we get nodejs starting to make noises in >>&

[Pkg-javascript-devel] Bug#934207: Bug#934207: Bug#934207: new upstream (12.8.0)

On വ്യാ, Dec 26, 2019 at 11:37, Raphael Hertzog wrote: What are your plans to upload nodejs 12.x to unstable? It is entanged in multiple transitions and one update needs a package in NEW. See https://wiki.debian.org/Javascript/Nodejs/Transitions -- Pkg-javascript-devel mailing list

Re: [Pkg-javascript-devel] [RFS] node-dispatch[1.0.6]

On വെ, Dec 20, 2019 at 18:15, abhijith sheheer wrote: Sorry. Got the name of package wrong. It is node-d3-dispatch and not node-dispatch. Looks good. I think from next time you can push to js-team directly for patch and minor updates. Please push to js-team. -- Pkg-javascript-devel

Re: [Pkg-javascript-devel] [RFS]node-d3-force[2.1.0]

On വെ, Dec 20, 2019 at 18:14, abhijith sheheer wrote: Updated node-d3-force from 1.2.1 to 2.1.0. Passes autopkgtest and sbuild. Link : https://salsa.debian.org/abspython-guest/node-d3-force Need review and sponsorship. Did you check if it is breaking any reverse build dependencies since

Re: [Pkg-javascript-devel] Sick and tired of hundreds of notifications

On 2019, ഡിസംബർ 17 3:10:30 AM IST, Utkarsh Gupta wrote: >Hi, > >On 20/10/19 9:03 am, Utkarsh Gupta wrote: >> Hello, >> >> On Sat, Oct 19, 2019, 13:05 Pirate Praveen >wrote: >> >>> On Fri, Oct 18, 2019 at 19:24, Utkarsh Gupta > >>> wr

Re: [Pkg-javascript-devel] Fwd:?==?utf-8?q? Re: Debian Janitor and us

On 2019, ഡിസംബർ 16 2:06:26 PM IST, Xavier wrote: >Hi all, > >You probably saw that I merged some patches provided by Debian-Janitor >bot (it fix some lintian warnings automatically). If you agree, we >could allow it to directly commit in our repositories. Some other teams >(see below) already

Re: [Pkg-javascript-devel] getting nodejs 12 in debian sid

On 2019, ഡിസംബർ 14 1:34:29 AM IST, "shirish शिरीष" wrote: >The numbering seems to be all over the place how is it that webpack >4.7 = acorn 5 and webpack 4.30 is ok with acorn 6 ? Or is it webpack >4.07 ok with acorn 5. Doesn't make much of a sense. Look at package.json for each version of

Re: [Pkg-javascript-devel] getting nodejs 12 in debian sid

On 2019, ഡിസംബർ 13 2:12:14 PM IST, "Jérémy Lal" wrote: >I'm concerned that acorn need webpack: >Could it be that the "node module" part of acorn need only rollup, and >the >"libjs part" need webpack ? I guess I did not explain it correctly. Current webpack 4.7 need acorn 5, and webpack 4.30

Re: [Pkg-javascript-devel] getting nodejs 12 in debian sid

On 2019, ഡിസംബർ 13 7:50:50 AM IST, "shirish शिरीष" wrote: >Any update as to when we get nodejs starting to make noises in >unstable/sid ? It is stalled. nodejs 12, needs acorn 6, acorn 6 transition needs rollup 1.10 and webpack 4.30. Webpack 4.30 needs webassemblyjs which is in NEW for 1

Re: [Pkg-javascript-devel] [RFS]node-color[3.1.2]

On വ്യാ, Dec 5, 2019 at 16:58, abhijith sheheer wrote: I have updated node-color to 3.1.2. It is lintian-error free and builds successfully in clean chroot. Updated package is pushed to : https://salsa.debian.org/abspython-guest/node-color/commits/master Need someone to review and sponsor

Re: [Pkg-javascript-devel] The (long) way to update rollup

On വെ, Nov 22, 2019 at 16:35, Xavier wrote: Le Vendredi, Novembre 22, 2019 16:03 CET, Pirate Praveen a écrit: On 2019, ഒക്‌ടോബർ 11 11:05:31 PM IST, Pirate Praveen wrote: With gitlab now working fine with d3 version 5.12, I think we are ready to upload rollup 1.0 to unstable. I'm

Re: [Pkg-javascript-devel] The (long) way to update rollup

On 2019, ഒക്‌ടോബർ 11 11:05:31 PM IST, Pirate Praveen wrote: With gitlab now working fine with d3 version 5.12, I think we are ready to upload rollup 1.0 to unstable. I'm planning to do the upload in next 2-3 days once I test gitlab with node-d3 version 5.12. Please check this list

Re: [Pkg-javascript-devel] Packaging node-timezone

On ഞാ, Nov 10, 2019 at 19:26, Paolo Greppi wrote: This means that the files you need are in the source of tzdata package. If node-timezone only needs that at build time, I wonder if you could build-depend on the source of tzdata ? You could ask tzdata maintainers to include those files

[Pkg-javascript-devel] Bug#943697: Bug#943697: RM: node-stringset -- RoM, abandoned upstream

On 2019, ഒക്‌ടോബർ 28 3:18:07 PM IST, Julien Puydt wrote: >Package: node-stringset > >Hi, > >I'm the maintainer of this package within the Debian Javascript >Maintainer team. It's not used anymore, abandoned upstream, so I'd like >to see it removed from unstable. Hi Julian, This should be

Re: [Pkg-javascript-devel] [RFS] node-qrcode-generator

On 2019, ഒക്‌ടോബർ 27 7:51:33 AM IST, Pirate Praveen wrote: > > >On 2019, ഒക്‌ടോബർ 26 11:54:48 PM IST, Xavier wrote: >>Le 26/10/2019 à 15:53, Nicolas Mora a écrit : >>> Hello js team, >>> >>> I need a sponsor to review the package node-qrcode-genera

Re: [Pkg-javascript-devel] [RFS] node-qrcode-generator

On 2019, ഒക്‌ടോബർ 26 11:54:48 PM IST, Xavier wrote: >Le 26/10/2019 à 15:53, Nicolas Mora a écrit : >> Hello js team, >> >> I need a sponsor to review the package node-qrcode-generator [1] and >> push it to NEW if possible. >> >> node-qrcode-generator is a javascript library which generates QR

Re: [Pkg-javascript-devel] Unable to build a react web application using webpack

On 2019, ഒക്‌ടോബർ 25 6:35:39 AM IST, Nicolas Mora wrote: >I have a web application written in react built with weback during the >packaging. > >If I build the package with the command "debuild -b -uc -us", the >packaging works. >But if I use sbuild to build the package, I have this weird

Re: [Pkg-javascript-devel] Unable to push code to newly created repositories in salsa.d.o/js-team/

On 2019, ഒക്‌ടോബർ 25 6:21:07 AM IST, Nicolas Mora wrote: >Hello, > >Le 19-10-16 à 20 h 10, Nicolas Mora a écrit : >> >> The problem is I don't have the settings menu in the new >repositories, >> yet I have maintainer credentials in the team. So I can't create a >> default branch for the

Re: [Pkg-javascript-devel] Bug#943389: node-lodash: source package does not contain upstream source

On Thu, Oct 24, 2019 at 19:05, Jonas Smedegaard wrote: Quoting Pirate Praveen (2019-10-24 18:42:17) On Thu, Oct 24, 2019 at 16:19, Jonas Smedegaard <mailto:d...@jones.dk>> wrote: > Quoting Pirate Praveen (2019-10-24 15:34:15) >> All files derived from source have t

[Pkg-javascript-devel] Bug#943389: Bug#943389: node-lodash: source package does not contain upstream source

On Thu, Oct 24, 2019 at 16:19, Jonas Smedegaard wrote: Quoting Pirate Praveen (2019-10-24 15:34:15) On Thu, Oct 24, 2019 at 11:40, Jonas Smedegaard <mailto:d...@jones.dk>> wrote: > The source package src:node-lodash states in its debian/copyright > file that its

[Pkg-javascript-devel] Bug#943389: Bug#943389: node-lodash: source package does not contain upstream source

On Thu, Oct 24, 2019 at 11:40, Jonas Smedegaard wrote: Package: node-lodash Version: 4.17.15+dfsg-1 Severity: serious Justification: Policy 2.1 -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 The source package src:node-lodash states in its debian/copyright file that its upstream source is

[Pkg-javascript-devel] Bug#943389: Bug#943389: node-lodash: source package does not contain upstream source

On Thu, Oct 24, 2019 at 11:40, Jonas Smedegaard wrote: Package: node-lodash Version: 4.17.15+dfsg-1 Severity: serious Justification: Policy 2.1 -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 The source package src:node-lodash states in its debian/copyright file that its upstream source is

[Pkg-javascript-devel] Bug#942809: Bug#942809: Why embed ts-node in node-typescript?

On Tue, Oct 22, 2019 at 16:46, Jonas Smedegaard wrote: Sounds reasonable to introduce psl as new _binary_ package (not embed in _binary_ package node-though-cookie and add "Provides: node-psl" hint): Upstream project has many seemingly unrelated reverse dependencies which are probably not

[Pkg-javascript-devel] Bug#935845: Bug#940708: Bug#935845: Bug#935845: not an RC bug; fix is easy: upgrade embedded lodash.cli

On Thu, Oct 24, 2019 at 10:05, Jonas Smedegaard wrote: What I criticise is *zero* indication of bundling for the package lodash: src:lodash 4.17.15+dfsg-1 I would strongly prefer using current bundling scheme for that: src:lodash 4.17.15+dfsg+~4.17.5-1 If lodash had had such a

Re: [Pkg-javascript-devel] Bug#935845: not an RC bug; fix is easy: upgrade embedded lodash.cli

On Thu, Oct 24, 2019 at 11:30, Pirate Praveen wrote: Its likely lodash-cli was updated later as our watch file is checking only 4.x version and uscan should have downloaded latest version anyway. As mentioned, it was not a problem with watch file as such. I think they stopped publishing

Re: [Pkg-javascript-devel] Bug#935845: not an RC bug; fix is easy: upgrade embedded lodash.cli

On Wed, Oct 23, 2019 at 22:31, Paolo Greppi wrote: Bringing this over to the mailing list ... On 23/10/19 22:07, Jonas Smedegaard wrote: Quoting Paolo Greppi (2019-10-23 21:18:37) ... The reason is that the bundled version of lodash-cli is out of date: grep version

[Pkg-javascript-devel] Bug#942809: Bug#942809: Bug#942809: Bug#942809: Why embed ts-node in node-typescript?

On Tue, Oct 22, 2019 at 11:26, Jonas Smedegaard wrote: javascript packages are treated differently from other languages. ruby packages get cleared in days or maximum weeks. Some JavaScript packages get cleared within hours. You shared your experience, I have seen your packages getting

[Pkg-javascript-devel] Bug#942809: Bug#942809: Bug#942809: Bug#942809: Why embed ts-node in node-typescript?

On Tue, Oct 22, 2019 at 11:15, Jonas Smedegaard wrote: Please do *not* hide code from ftpmasters by embedding it in other packages - that is foul play, and you risk getting banned from Debian! - put together packages that belong together; I am not sure here, but wouldn't it be fine to

[Pkg-javascript-devel] Bug#942809: Bug#942809: Bug#942809: Why embed ts-node in node-typescript?

On Tue, Oct 22, 2019 at 10:26, Julien Puydt wrote: Le mardi 22 octobre 2019 à 10:01 +0200, Xavier a écrit : Le Mardi, Octobre 22, 2019 09:10 CEST, Julien Puydt < julien.pu...@laposte.net > a écrit: > If you want to have ts-node, why not package it

Re: [Pkg-javascript-devel] [review(rollup-transitions)] node-rollup-plugin-babel

On Fri, Oct 18, 2019 at 13:22, Nilesh Patra wrote: > This commit -> does not seem right. Do you really need name option for cjs and es builds? > Even if you need, I think you

Re: [Pkg-javascript-devel] Sick and tired of hundreds of notifications

On Fri, Oct 18, 2019 at 19:24, Utkarsh Gupta wrote: Hey, It's been quite a while since I've been trying to *not* write this, but realizing this would never end, so here.. Can we *please* shift to a sane mailing list (maybe something like debian-js@l.d.o ?) where

Re: [Pkg-javascript-devel] node-webassemblyjs_1.8.5+dfsg-1_amd64.changes is NEW

On 2019, ഒക്‌ടോബർ 18 2:34:20 PM IST, Debian FTP Masters wrote: >binary:node-webassemblyjs is NEW. >binary:node-webassemblyjs is NEW. >source:node-webassemblyjs is NEW. > >Your package has been put into the NEW queue, which requires manual >action >from the ftpteam to process. The upload was

Re: [Pkg-javascript-devel] Tracking status of js transitions for bullseye

On Wed, Oct 16, 2019 at 21:22, Pirate Praveen wrote: On Tue, Oct 15, 2019 at 22:05, Pirate Praveen wrote: The major challenge I see with Webpack 4.30 is addition of large number of webassembly dependencies. Any ideas? I have not looked close enough yet (last time I chose 4.7 to avoid

[Pkg-javascript-devel] Bug#942523: fallback to npm registry tarballs when upstream git repo is missing

Package: pkg-js-tools version: 0.9.17 $ add-node-component -if babel-plugin-mamacro Thread 1 terminated abnormally: No repo found for 0.0.7 version at /usr/share/perl5/Debian/PkgJs/Npm.pm line 65. Component babel-plugin-mamacro not found in npm registry at /usr/bin/add-node-component line 173.

Re: [Pkg-javascript-devel] Tracking status of js transitions for bullseye

On Tue, Oct 15, 2019 at 22:05, Pirate Praveen wrote: The major challenge I see with Webpack 4.30 is addition of large number of webassembly dependencies. Any ideas? I have not looked close enough yet (last time I chose 4.7 to avoid running into these dependencies). I first tried adding

Re: [Pkg-javascript-devel] tsc help needed

On Tue, Oct 15, 2019 at 21:17, Xavier wrote: After many tries, none of these solutions work... If I replace domhandler in node_modules with version from npm registry, it works. Weirdly I can't really see any difference between the two though. tsconfig.json was not installed in the debian

Re: [Pkg-javascript-devel] Error in i18next-xhr-backend test

On Thu, Oct 10, 2019 at 22:50, Nicolas Mora wrote: Hello, In the package node-i18next-xhr-backend [1] I'm working on, I have this error during the dh_test phase: dh_auto_test --buildsystem=nodejs /usr/bin/node -e require\(\"./.\"\) internal/modules/cjs/loader.js:638 throw

[Pkg-javascript-devel] Tracking status of js transitions for bullseye

Hi team, I have created a wiki page to track the stuatus of all transitions here -> With the last many days work, rollup 1.10.1 is almost ready (there are some packages that needs fixing but nothing major). But we will need to wait for

[Pkg-javascript-devel] Bug#942389: --output is now --file

Control: tags -1 patch The following patch fixes the build diff --git a/debian/nodejs/should-equal/build b/debian/nodejs/should-equal/build index 37366fd..567841b 100644 --- a/debian/nodejs/should-equal/build +++ b/debian/nodejs/should-equal/build @@ -1,2 +1,2 @@ -rollup --format=cjs

[Pkg-javascript-devel] Bug#942389: rollup 1.10 transition: should.js build fails with You have passed an unrecognized option

package: should.js version: 13.2.3~dfsg-1 severity: important I think git repo is not having the latest commits, so not sure if -2 is different, (!) You have passed an unrecognized option Unknown CLI flag: 0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18. Allowed options:

Re: [Pkg-javascript-devel] tsc help needed

On Tue, Oct 15, 2019 at 13:30, Pirate Praveen wrote: On Tue, Oct 15, 2019 at 11:40, Pirate Praveen wrote: I have seen this error. I think tsc does not check this field. It needs index.d.ts in the root directory. Create a symbolic link for that. I think I did this for one of the rollup

[Pkg-javascript-devel] Bug#942361: Bug#942361: I think .d.ts files should be included by default

On Tue, Oct 15, 2019 at 13:27, Pirate Praveen wrote: On Tue, Oct 15, 2019 at 13:23, Pirate Praveen wrote: Even though package.json#files mentions dist, I think .d.ts was filtered out. I found the problem, package.json#scripts had a cp command too to copy d.ts, which I missed. Though

Re: [Pkg-javascript-devel] tsc help needed

On Tue, Oct 15, 2019 at 11:40, Pirate Praveen wrote: I have seen this error. I think tsc does not check this field. It needs index.d.ts in the root directory. Create a symbolic link for that. I think I did this for one of the rollup build deps, I will check which one. Check node

[Pkg-javascript-devel] Bug#942361: I think .d.ts files should be included by default

On Tue, Oct 15, 2019 at 13:23, Pirate Praveen wrote: Even though package.json#files mentions dist, I think .d.ts was filtered out. I found the problem, package.json#scripts had a cp command too to copy d.ts, which I missed. Though original request to check typings field is still valid I

[Pkg-javascript-devel] Bug#942361: I think .d.ts files should be included by default

Even though package.json#files mentions dist, I think .d.ts was filtered out. -- Pkg-javascript-devel mailing list Pkg-javascript-devel@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel

[Pkg-javascript-devel] Bug#942361: pkg-js-tools auto install should install package.json#typings too when present

Package: pkg-js-tools version: 0.9.16 Similar to #941359, we also need to install typings: field too. Example package is node-rollup-pluginutils -- Pkg-javascript-devel mailing list Pkg-javascript-devel@alioth-lists.debian.net

Re: [Pkg-javascript-devel] tsc help needed

On 2019, ഒക്‌ടോബർ 15 12:43:08 AM IST, Xavier wrote: >Hi all, > >node-entities migration is blocked due to node-htmlparser2. To update >it >I updated node-domelementtype, node-domhandler, node-dom-serializer and >node-domutils. Whil trying to build node-domutils, I got this: > >tsc

[Pkg-javascript-devel] Bug#942302: Bug#942302: Processed: Update node-rollup-pluginutils to 2.6.0 or later

On Mon, Oct 14, 2019 at 15:27, Pirate Praveen wrote: Just tried debian/nodejs/extlinks (and --with nodejs) instead of patching rollup.config.js, but it fails the same way. dh_auto_configure --buildsystem=nodejs mkdir node_modules ln -s /usr/share/nodejs/micromatch

[Pkg-javascript-devel] Bug#942302: Processed: Update node-rollup-pluginutils to 2.6.0 or later

Just tried debian/nodejs/extlinks (and --with nodejs) instead of patching rollup.config.js, but it fails the same way. dh_auto_configure --buildsystem=nodejs mkdir node_modules ln -s /usr/share/nodejs/micromatch ./node_modules/ debian/rules override_dh_auto_build make[1]:

[Pkg-javascript-devel] Bug#942302: Update node-rollup-pluginutils to 2.6.0 or later

Package: node-rollup-pluginutils version: 2.3.3-4 severity: important Control: block 942200 by -1 As part of rollup 1.x transition, we need rollup-pluginutils 2.6 or greater for rollup 1.10.1 But when trying to build this version, build fails with this error rollup -c src/index.ts →

[Pkg-javascript-devel] Bug#942200: Bug#942200: Bug#942200: Bug#942200: rollup 1.0 transition: node-d3 built with rollup 1.0 gives error in test

On Mon, Oct 14, 2019 at 10:26, Xavier wrote: tsc has some problem to parse /usr/share. Try to add this module to debian/nodejs/extlinks I think the problem is in node-rollup-pluginutils itself (rollup was showing Unresolved dependency error for micromatch), but when trying to add system

[Pkg-javascript-devel] Bug#942200: Bug#942200: Bug#942200: rollup 1.0 transition: node-d3 built with rollup 1.0 gives error in test

On Sun, Oct 13, 2019 at 19:13, Xavier wrote: Thanks a lot for your work ! You are welcome :) We'll need to update node-rollup-pluginutils to 2.6 and drop src_babel generation as tsc can consume ES module directly. I'm going to try this tomorrow. After updating node-rollup-pluginutils,

[Pkg-javascript-devel] Bug#942200: Bug#942200: rollup 1.0 transition: node-d3 built with rollup 1.0 gives error in test

On Sun, Oct 13, 2019 at 20:15, Pirate Praveen wrote: This seems like a bug in rollup 1.0.2. Using with rollup 1.0.2 in package.json, npm i; npm run test also fails. Works fine with rollup 1.8. Now trying to update to 1.10.1 (which also works). Found debian/nodejs/./build cd

[Pkg-javascript-devel] Bug#942200: rollup 1.0 transition: node-d3 built with rollup 1.0 gives error in test

Control: reassign -1 rollup Control: found -1 1.0.2-1 Control: retitle -1 rollup 1.0.2 creates broken bundle for node-d3 On Sun, Oct 13, 2019 at 16:48, Pirate Praveen wrote: On Sat, 12 Oct 2019 13:04:10 +0530 Pirate Praveen mailto:prav...@onenetbeyond.org>> wrote: package: node-d3 v

[Pkg-javascript-devel] Bug#942200: rollup 1.0 transition: node-d3 built with rollup 1.0 gives error in test

On Sat, 12 Oct 2019 13:04:10 +0530 Pirate Praveen wrote: > package: node-d3 > version: 4.13.0-10 With node-d3 5.12, build succeeds and one test fails, # version matches package.json ok 1 should be equal # d3.event is a getter for d3Selection.event ok 2 should be equal not ok 3 should be

[Pkg-javascript-devel] Bug#942259: rollup 1.x transition: node-locate-character build fails with Error: You must supply options.input to rollup

package: node-locate-character version: 2.0.1-6 severity: important With rollup 1.0 in experimental, build failed with this error, please fix this error before uploading rollup 1.0 to unstable. rollup -c (!) You have passed an unrecognized option Unknown input option: entry, moduleName,

Re: [Pkg-javascript-devel] build node-i18next with webpack instead or rollup?

On Wed, Oct 9, 2019 at 15:21, Nicolas Mora wrote: Le 2019-10-09 13:02, Xavier a écrit : No but it's a git-buildpackage bug. Commit the good file using: $ pristine-tar commit ../node-i18next-17.0.18.tar.gz upstream/17.0.18 Then push to salsa (using `salsa push` which pushes all what is

Re: [Pkg-javascript-devel] [review(rollup-transitions)] node-rollup-plugin-babel

On Sat, Oct 12, 2019 at 17:25, Nilesh Patra wrote: Hi I was working on node-rollup-plugin-babel for rollup transitions to 1.0.2. I have pushed my changes to: .It would be great if it can be reviewed. This commit ->

[Pkg-javascript-devel] Bug#942200: rollup 1.0 transition: node-d3 built with rollup 1.0 gives error in test

package: node-d3 version: 4.13.0-10 severity: important With rollup 1.0 in experimental, build trew some warning and test failed Found debian/nodejs/./build cd ./. && sh -e debian/nodejs/./build index → build/d3.js... (!) node-resolve plugin: The onwrite hook used by plugin

[Pkg-javascript-devel] Bug#942199: rollup 1.0 transition: node-rollup-plugin-babel fails to build with Error: You must supply options.input to rollup

package: node-rollup-plugin-babel version: 3.0.3-3 severity: important With rollup 1.0.2-1 in experimental, we get this error when building, Found debian/nodejs/./build cd ./. && sh -e debian/nodejs/./build (!) You have passed an unrecognized option Unknown input option: entry, targets,

Re: [Pkg-javascript-devel] RFS: node-d3-geo[1.11.3]

On Fri, Oct 11, 2019 at 19:43, abhijith sheheer wrote: Dear Mentors/Sponsors, I have updated the node-d3-geo from 1.11.3 to 1.11.6 . It's lintian error free and I looking for a sponsor for the package. More info regarding the package : I

Re: [Pkg-javascript-devel] The (long) way to update rollup

On Wed, Oct 9, 2019 at 20:33, Pirate Praveen wrote: Hi team, rollup 0.56 is in unstable/testing and 0.68.2 in experimental. Need help with fixing the packages that fail with new version. List here <https://wiki.debian.org/Javascript/Nodejs/Transitions/Rollup1> rollup

[Pkg-javascript-devel] Bug#942170: Update node-buble to a version compatible with acorn 6

Package: node-buble version: 0.19.4-3 Severity: important Control: block 942169 by -1 node-acorn 6 is in experimental and rollup 1.0 will soon be uploaded to experimental. Some packages using node-buble failed to build with this error. Other packaged like node-uri-js, node-d3-color etc which

[Pkg-javascript-devel] Bug#942169: Update rollup to 1.0

Package: rollup Version: 0.68.2-2 Control: block 911367 by -1 I have started the update process in master-1.0 branch. -- Pkg-javascript-devel mailing list Pkg-javascript-devel@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel

[Pkg-javascript-devel] Bug#911367: Bug#911367: New upstream is out

Control: retitle -1 "Update node-acorn to 6.x" On Sat, 20 Oct 2018 16:46:55 +0200 Bastien ROUCARIES wrote: > Note that it will need a hug testing due to change of API for plugins. I have started updating rollup to 1.0.2 in (master-1.0 branch), which switches to acorn 6. --

Re: [Pkg-javascript-devel] Rollup do _not_ need migrating to terser from UglifyJS

is that as part of the Rollup work, Pirate Praveen provided a patch for Leaflet.Markercluster which involved switching from UglifyJS to Terser, and I want to emphasize that such change is _not_ necessary and I recommend switching back if similar tricks was done for other libraries. I have seen some

Re: [Pkg-javascript-devel] [review(rollup transitions)] popper.js

On Wed, Oct 2, 2019 at 21:16, Xavier wrote: Le 02/10/2019 à 16:06, Nilesh Patra a écrit : I have pushed changes to local fork here - salsa.debian.net/gi-boi-guest/popper.js <>

[Pkg-javascript-devel] Bug#942045: Bug#942045: rollup 0.68.2 transition: build fails with TypeError: magic_string_1.SourceMap is not a constructor

Control: forwarded -1 Send the patch upstream as well. -- Pkg-javascript-devel mailing list Pkg-javascript-devel@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel

[Pkg-javascript-devel] Bug#942045: rollup 0.68.2 transition: build fails with TypeError: magic_string_1.SourceMap is not a constructor

Control: affects -1 rollup On Thu, 10 Oct 2019 14:16:44 +0530 Pirate Praveen wrote: > Control: reassign -1 node-magic-string > > I think this comes from the inconsistent exports in es.js and cjs.js > > es.js has this line at the end, > > export { Bundle, SourceMap }; >

[Pkg-javascript-devel] Bug#942045: rollup 0.68.2 transition: build fails with TypeError: magic_string_1.SourceMap is not a constructor

Control: reassign -1 node-magic-string I think this comes from the inconsistent exports in es.js and cjs.js es.js has this line at the end, export { Bundle, SourceMap }; but cjs.js or umd.js does not export these. -- Pkg-javascript-devel mailing list

Re: [Pkg-javascript-devel] The (long) way to update rollup

Hi team, rollup 0.56 is in unstable/testing and 0.68.2 in experimental. Need help with fixing the packages that fail with new version. List here Thanks Praveen -- Pkg-javascript-devel mailing list

Re: [Pkg-javascript-devel] build node-i18next with webpack instead or rollup?

On Wed, Oct 9, 2019 at 07:08, Nicolas Mora wrote: Le 19-10-09 à 02 h 47, Pirate Praveen a écrit : Well, if you had not pushed to js-team, squashing makes sense as it require force push. It is not recommended to force push to team repo after it is published. In this case since we have

[Pkg-javascript-devel] Bug#931571: Bug#931571: Bug#931571: rollup: please update to upstream release 0.61.0 or newer

On Sat, 05 Oct 2019 19:34:48 +0530 Pirate Praveen wrote: > > > On Sat, Oct 5, 2019 at 14:10, Pirate Praveen > wrote: > > I fixed this error with the following patch, it'd be good if someone > > can confirm this is okay. > > > > Now with master-0.68 bran

Re: [Pkg-javascript-devel] build node-i18next with webpack instead or rollup?

On 2019, ഒക്‌ടോബർ 9 3:23:33 AM IST, Nicolas Mora wrote: >although I didn't squash the commits in the master branch, only pushed >as it is in my personnal repo. Should I rebase all the commits in the >master branch from the start? Well, if you had not pushed to js-team, squashing makes sense as

[Pkg-javascript-devel] Bug#941700: Bug#941700: Bug#941700: Update babel to version 7

On Sun, Oct 6, 2019 at 15:18, Pirate Praveen wrote: On Fri, 04 Oct 2019 11:27:58 +0530 Pirate Praveen mailto:prav...@onenetbeyond.org>> wrote: We already started the update work, but since it needs gulp 4, we are stuck (we are not able to fix gulp 4 errors). Alternatively we cou

Re: [Pkg-javascript-devel] build node-i18next with webpack instead or rollup?

On Mon, Oct 7, 2019 at 18:32, Nicolas Mora wrote: Indeed it's just warning messages, I've read the build log too fast, the error was because of invalid tests. The upstream package uses karma to run tests so I had to disable testing in the package build. I let a note as a reminder for the

[Pkg-javascript-devel] Bug#941119: Bug#941119: Wontfix

On 2019, ഒക്‌ടോബർ 7 11:36:16 PM IST, Xavier wrote: >Le 04/10/2019 à 19:11, Pirate Praveen a écrit : >> On Mon, 30 Sep 2019 22:59:08 +0200 Xavier wrote: >>> 941119: error is on npm registry side >> >> It does not work for any module. npm and other tools still w

Re: [Pkg-javascript-devel] build node-i18next with webpack instead or rollup?

On 2019, ഒക്‌ടോബർ 7 7:17:30 PM IST, Nicolas Mora wrote: >Hi, > >Le 19-10-07 à 04 h 02, Pirate Praveen a écrit : >> >> See >> >https://salsa.debian.org/ruby-team/rails/blob/master/debian/patches/0002-disable-uglify-in-activestorage-rollup-config-js.patch >> t

Re: [Pkg-javascript-devel] build node-i18next with webpack instead or rollup?

On Sun, Oct 6, 2019 at 22:47, Nicolas Mora wrote: Hello JS team, I was able to make a package for i18next here: Thanks to Pirate's feedback, I now build the bundle with rollup, but the minified bundle is created with

Re: [Pkg-javascript-devel] build node-i18next with webpack instead or rollup?

On Sun, Oct 6, 2019 at 08:57, Nicolas Mora wrote: Hello, I'm trying to package i18next for Debian [1]. The upstream dev use rollup to build the i18next.js file with rollup-plugin-terser. Unfortunately, rollup-plugin-terser isn't in Debian yet and requires a lot of unpackaged dependencies.

[Pkg-javascript-devel] Bug#941841: Update node-rollup-plugin-babel to 4.x (required for updating babel to 7.x)

Package: node-rollup-plugin-babel Version: 3.0.3-2 Severity: important Control: block 941700 by -1 Please update this package to 4.x version to update node-babel to 7.x -- Pkg-javascript-devel mailing list Pkg-javascript-devel@alioth-lists.debian.net

[Pkg-javascript-devel] Bug#941700: Bug#941700: Update babel to version 7

On Fri, 04 Oct 2019 11:27:58 +0530 Pirate Praveen wrote: > We already started the update work, but since it needs gulp 4, we are stuck > (we are not able to fix gulp 4 errors). Alternatively we could try to skip > gulp. With gulp 4.0.2-3, gulp build [14:53:55] Local gulp not found i

[Pkg-javascript-devel] Bug#929811: Port build to gulp 4 (transition coming)

Control: block -1 by 941700 On Fri, 31 May 2019 20:31:55 +0500 Pirate Praveen wrote: > package: node-postcss > version: 6.0.23-1 > severity: important > > gulp 4.0 is now available in experimental. We'd like to upload it to > unstable (after freeze) when all reverse

[Pkg-javascript-devel] Bug#929829: gulp 4 cannot build node-babel 7 - Cannot convert undefined or null to object

On 2019, ഒക്‌ടോബർ 6 3:38:47 AM IST, Evgeny Kapun wrote: >> [15:37:17] Cannot convert undefined or null to object > >After checking the code, I found the root cause of this error. Awesome! We have been trying to find the root cause for some time. >The error is caused by NPM package

[Pkg-javascript-devel] Bug#931571: Bug#931571: Bug#931571: rollup: please update to upstream release 0.61.0 or newer

On Sat, Oct 5, 2019 at 14:10, Pirate Praveen wrote: I fixed this error with the following patch, it'd be good if someone can confirm this is okay. Now with master-0.68 branch simple bundling with command line works but more complex builds fail. /usr/share/nodejs/rollup/bin/src/run

[Pkg-javascript-devel] Bug#931571: Bug#931571: rollup: please update to upstream release 0.61.0 or newer

On Sat, Oct 5, 2019 at 13:28, Pirate Praveen wrote: On Sun, 07 Jul 2019 16:21:14 -0300 Jonas Smedegaard <mailto:d...@jones.dk>> wrote: Please update to upstream release 0.61.0 or newer, as this is needed by node-terser. I'm trying to update to 0.68.2 in master-0.68 branch

[Pkg-javascript-devel] Bug#931571: rollup: please update to upstream release 0.61.0 or newer

On Sun, 07 Jul 2019 16:21:14 -0300 Jonas Smedegaard wrote: > Please update to upstream release 0.61.0 or newer, as this is needed by > node-terser. I'm trying to update to 0.68.2 in master-0.68 branch, https://salsa.debian.org/js-team/node-rollup/commits/master-0.68 tsc command fails with this

[Pkg-javascript-devel] Bug#941601: rollup 0.56 transition: Add node-rollup-plugin-json to build depends and fix 'format is now output.format' error

Control: severity -1 serious On Wed, 02 Oct 2019 21:16:33 +0530 Pirate Praveen wrote: > Package: leaflet-markercluster > Version: 1.4.1~dfsg-6 > Severity: important rollup 0.56.3-2 is in unstable and raising severity accordingly. -- Pkg-javascript-devel mailing list Pkg-javascr

[Pkg-javascript-devel] Bug#941604: rollup 0.56 transition: rainbow.js build fails with 'Unknown option found: moduleName, dest'

Control: severity -1 serious On Wed, 02 Oct 2019 21:51:01 +0530 Pirate Praveen wrote: > Package: rainbow.js > version: 2.1.4+ds-1 > severity: important > > rainbow.js fails with rollup 0.56 currently in experimental. Please > update your package to work with rollup 0.56

[Pkg-javascript-devel] Bug#941119: Wontfix

On Mon, 30 Sep 2019 22:59:08 +0200 Xavier wrote: > 941119: error is on npm registry side It does not work for any module. npm and other tools still work with the registry so I think we need to work around this or at least report the issue to npmjs.com -- Pkg-javascript-devel mailing list

[Pkg-javascript-devel] Bug#941700: Bug#941700: Update babel to version 7

Control: block -1 by 929829 Control: tags -1 help On 2019, ഒക്‌ടോബർ 4 3:22:23 AM IST, Evgeny Kapun wrote: >Source: node-babel >Version: 6.26.0+dfsg-3 >Severity: important > >Babel 7 was released more than a year ago, so perhaps it's time to >package the new version. We already started the

Re: [Pkg-javascript-devel] Troubles with tsc

On Thu, 3 Oct, 2019 at 10:31, Pirate Praveen wrote: The directory it is expecting is, /usr/share/nodejs/typescript/lib (if you hard code this path then it works). Should we install types in this directory? Just tested, it does not work. Added @types/xxx and xxx in this path and even

Re: [Pkg-javascript-devel] Troubles with tsc

On Wed, 2 Oct, 2019 at 11:30, Julien Puydt wrote: Le mercredi 02 octobre 2019 à 07:12 +0200, Xavier a écrit : Hi all, when trying to update node-css-what, it's OK with testing but unstable give me this: tsc error TS2318: Cannot find global type 'Array'. error TS2318: Cannot find

Re: [Pkg-javascript-devel] ?= [review(rollup=?utf-8?q? transitions)] twitter-bootstrap4

On Wed, 2 Oct, 2019 at 21:36, Xavier wrote: Reviewed and fixed. Sadly I forgot to bring my yubikey here. If another DD can sign this, go ahead. Else I'll sign it tomorrow evening Uploaded, thanks to both! -- Pkg-javascript-devel mailing list Pkg-javascript-devel@alioth-lists.debian.net

[Pkg-javascript-devel] Bug#941604: rollup 0.56 transition: rainbow.js build fails with 'Unknown option found: moduleName, dest'

Package: rainbow.js version: 2.1.4+ds-1 severity: important rainbow.js fails with rollup 0.56 currently in experimental. Please update your package to work with rollup 0.56. The error message is, NODE_PATH=debian/node_modules gulp pack [16:17:26] Local gulp not found in /<> [16:17:26] Try

[Pkg-javascript-devel] Bug#930634: Bug#930634: Bug#930634: Bug#930634: Build failures with rollup 0.56

On Mon, 30 Sep 2019 19:49:38 +0530 Pirate Praveen wrote: > The following fail (18/77 reverse build dependencies), but should work > after adding the required plugin as build dependency. > > leaflet leaflet-markercluster node-d3 node-immutable-tuple > node-magic-string node-m

<    1   2   3   4   5   6   7   8   9   10   >