Re: [Pkg-javascript-devel] node-yarnpkg_1.22.4-6_source.changes ACCEPTED into unstable

[Pirate Praveen]

On 2020, ഡിസംബർ 18 5:14:57 PM IST, Pirate Praveen  
wrote:
>
>
>On Fri, Dec 18, 2020 at 12:41, Xavier  wrote:
>> Hi,
>> 
>> I still see one problem: yarnpkg seems to depends on
>> node-babel-plugin-transform-strict-mode
>
>Thanks for checking, with 
>babel-plugin-transform-inline-imports-commonjs removed, we can remove 
>this build dependency. I will remove it in the next upload.

This is fixed in the last upload.

Akshay wrote about his experience here

https://asd.learnlearn.in/first-debian-contribution/
-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.

-- 
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#977670: Bug#977670: jest: should explicitly (build-)depend on needed babel modules

[Pirate Praveen]

On Fri, Dec 18, 2020 at 19:05, Jonas Smedegaard  wrote:

Sounds like a change specific to backports, not for official Debian.


Backports is official debian, it is backports.debian.org and not 
backports.debian.net. Though if you don't care about making it harder 
than necessary for people maintaining backports, that is your choice. 
But that does not make it unofficial. And this is not exactly team 
maintenance either.


--
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#977670: Bug#977670: jest: should explicitly (build-)depend on needed babel modules

[Pirate Praveen]

On Fri, Dec 18, 2020 at 23:39, Pirate Praveen 
 wrote:



On Fri, Dec 18, 2020 at 19:05, Jonas Smedegaard  wrote:

Sounds like a change specific to backports, not for official Debian.


Backports is official debian, it is backports.debian.org and not 
backports.debian.net. Though if you don't care about making it harder 
than necessary for people maintaining backports, that is your choice. 
But that does not make it unofficial. And this is not exactly team 
maintenance either.


Also as seen in #977677, it even caused ftbfs in unstable. So you are 
introducing regressions without even testing them.


--
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#977706: path-parse is now included in node-resolve

[Pirate Praveen]

Package: npm
Version: 7.2.0+ds-1

node-resolve 1.19.0+~cs5.20.8 now includes path-parse module so it may 
be dropped from npm.


--
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#977781: Bug#977781: real issue is, it does not pull not-yet-cached modules

[Pirate Praveen]

On 2020, ഡിസംബർ 21 1:46:31 PM IST, Paolo Greppi  wrote:
>Hi Pirate,
>
>what you want to put in ~/.yarnrc.yml could be installed globally to 
>/etc/yarn/config or /etc/yarnrc, but that does not actually fix it.

I agree, I wanted to see if it can be used to update to yarn 2 (so yarnpkg just 
becomes an installer for yarn 2). I was able to use yarn 2 successfully in 
gitlab.

This commit makes the switch to yarn 2.

https://salsa.debian.org/ruby-team/gitlab/-/commit/43df5d0233cef3936b3d5abab334c5fdeeafa717

>I think the real issue is that it does not pull not-yet-cached modules.

I think the failure is after it downloaded. I can see some files in 
~/.cache/yarn created after it is cleaned after yarnpkg add. Could it be a 
problem with extracting the tar ?

>To reproduce:
>
>   # clear cache
>   rm -rf ~/.cache/yarn
>   # actual test
>   cd `mktemp -d`
>   yarnpkg init -y
>   yarnpkg add d3-color
>
>Adding the nodeLinker: "node-modules" option to ~/.yarnrc.yml or the global 
>locations does not help.

It helps if you switch to yarn 2 by running yarnpkg set version berry. See the 
patch linked above for gitlab. It was failing with yarn 1, but worked after 
switching to berry.

We cannot set version to berry globally, it has to be set per project.

>It would be interesting to debug the JavaScript execution after it prints 
>"Fetching packages..."
>

I think we need to revert this patch and fix the error.

https://salsa.debian.org/js-team/node-yarnpkg/-/commit/c122f5c26eefb0b68e0c680eb0d65aae86ef4f9e
-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.

-- 
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#977781: yarnpkg: fails to download modules

[Pirate Praveen]

On Mon, 21 Dec 2020 13:15:46 +0530 Akshay S Dinesh  wrote:
> > Since yarnpkg add command did not return an error, the autpkgtest was 
> > succeeding even though it did not add any modules to node_modules 
> > directory.
> > 
> 
> 
> I did a bisect (sort of).
> 
> Removing cache is not an issue till commit 232ee703 (New upstream version 
> 1.22.4+debian)
> 
> But, it is an issue at commit d40971ee (Refresh patches (remove parts no 
> longer needed)
> 
> The one commit in between them - New upstream version 1.22.10+~cs18.39.16 ( 
> 40af4cca ) could be the one which introduced this.

1.22.4+debian is yarn prebuilt with babel 6 (targeting contrib, see 
master-contrib branch).

-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.-- 
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#977688: node-css-loader: please embed additional postcss extensions

[Pirate Praveen]

On Fri, 18 Dec 2020 23:10:30 +0100 Jonas Smedegaard  wrote:
> Package: node-css-loader
> Version: 3.2.1+~cs21.3.8.1-2
> Severity: wishlist
>
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA512
>
> I need these postcss-related modules not yet in Debian:
>
>  postcss-loader
>  postcss-preset-env
>  postcss-strip-inline-comments
>
> They all have seemingly similar dependencies and build-dependencies -
> notably they build-depend on babel same as node-css-loader.
>
> Please consider embdding these postcss modules with node-css-loader.

I'd like to update css-loader to latest upstream release/postcss 8 
transition before I work on this.


--
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#977770: pdf.js-common is probably obsolete

[Pirate Praveen]

Package: pdf.js-common
Version: 2.6.347+dfsg-3
Severity: normal

I think this binary package is left over from the need to share files 
between xul-ext-pdf.js and libjs-pdf.


https://packages.debian.org/source/oldstable/pdf.js

With xul-ext-pdf.js removed, I think we can remove pdf.js-common as 
well adn ship relevant files in libjs-pdf.


--
Pkg-javascript-devel mailing list
Pkg-javascript-devel@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel

Re: [Pkg-javascript-devel] node-resolve_1.19.0+~cs5.20.8-2_sourceonly.changes ACCEPTED into unstable

[Pirate Praveen]

On Sun, Dec 20, 2020 at 10:28 am, Xavier  wrote:

Le 20/12/2020 à 10:18, Debian FTP Masters a écrit :



 Accepted:

 Format: 1.8
 Date: Sun, 20 Dec 2020 09:54:23 +0100
 Source: node-resolve
 Architecture: source
 Version: 1.19.0+~cs5.20.8-2
 Distribution: unstable
 Urgency: medium
 Maintainer: Debian Javascript Maintainers 


 Changed-By: Xavier Guimard 
 Changes:
  node-resolve (1.19.0+~cs5.20.8-2) unstable; urgency=medium
  .
* Team upload
* Restore dependency to node-has (node-function-base): this broke
  is-core-module (fix debci regressions)


Another lack of autopkgtest check, yet seen by salsa-ci:
https://salsa.debian.org/js-team/node-resolve/-/jobs/1258549


It'd be good if we add a comment in control why we add a dependency not 
present in package.json. For example


# For embedded component foo
node-bar

This will make it easy for us to remove unused dependencies when new 
upstream versions remove dependencies.




--
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#977772: pdf.js: ftbfs with node-postcss 8/node-css-loader 5 in experimental

[Pirate Praveen]

Package: pdf.js
Version: 2.6.347+dfsg-3
Severity: important

With node-css-loader 5.0 from experimental, pdf.js ftbfs with this error

This require node-autoprefixer >= 10.1 and I'm working on updating it 
currently.


### Creating generic viewer
[13:29:04] '' errored after 369 ms
[13:29:04] TypeError in plugin "gulp-postcss"
Message:
   Cannot read property 'unprefixed' of undefined
Details:
   postcssNode: position: absolute
   fileName: viewer.css
   domainEmitter: [object Object]
   domainThrown: false

Stack:
TypeError: Cannot read property 'unprefixed' of undefined
   at /<>/viewer.css:17:3
   at Prefixes.unprefixed 
(/usr/share/nodejs/autoprefixer/lib/prefixes.js:445:39)

   at /usr/share/nodejs/autoprefixer/lib/processor.js:438:40
   at /usr/share/nodejs/postcss/lib/container.js:91:18
   at /usr/share/nodejs/postcss/lib/container.js:74:18
   at Rule.each (/usr/share/nodejs/postcss/lib/container.js:60:16)
   at Rule.walk (/usr/share/nodejs/postcss/lib/container.js:71:17)
   at /usr/share/nodejs/postcss/lib/container.js:79:24
   at Root.each (/usr/share/nodejs/postcss/lib/container.js:60:16)
   at Root.walk (/usr/share/nodejs/postcss/lib/container.js:71:17)
   at Root.walkDecls (/usr/share/nodejs/postcss/lib/container.js:89:19)
[13:29:04] 'generic' errored after 1.04 s
[13:29:04] 'dist-pre' errored after 1.05 s
make[1]: *** [debian/rules:9: override_dh_auto_build] Error 1
make[1]: Leaving directory '/<>'
make: *** [debian/rules:6: binary] Error 2
dpkg-buildpackage: error: debian/rules binary subprocess returned exit 
status 2


Build finished at 2020-12-20T13:29:04Z

full build log is attached

sbuild (Debian sbuild) 0.79.1 (22 April 2020) on mahishi

+==+
| pdf.js 2.6.347+dfsg-3 (amd64)Sun, 20 Dec 2020 13:28:25 + |
+==+

Package: pdf.js
Version: 2.6.347+dfsg-3
Source Version: 2.6.347+dfsg-3
Distribution: experimental
Machine Architecture: amd64
Host Architecture: amd64
Build Architecture: amd64
Build Type: binary

I: NOTICE: Log filtering will replace 
'var/run/schroot/mount/unstable-amd64-sbuild-a333b684-9a4f-421d-ad91-d791c4f7dc10'
 with '<>'
I: NOTICE: Log filtering will replace 'build/pdf.js-bb4Agq/resolver-VC4dEL' 
with '<>'

+--+
| Update chroot|
+--+

Get:1 file:/build/pdf.js-bb4Agq/resolver-zhpIk1/apt_archive ./ InRelease
Ign:1 file:/build/pdf.js-bb4Agq/resolver-zhpIk1/apt_archive ./ InRelease
Get:2 file:/build/pdf.js-bb4Agq/resolver-zhpIk1/apt_archive ./ Release [951 B]
Get:2 file:/build/pdf.js-bb4Agq/resolver-zhpIk1/apt_archive ./ Release [951 B]
Get:3 file:/build/pdf.js-bb4Agq/resolver-zhpIk1/apt_archive ./ Release.gpg
Ign:3 file:/build/pdf.js-bb4Agq/resolver-zhpIk1/apt_archive ./ Release.gpg
Get:4 file:/build/pdf.js-bb4Agq/resolver-zhpIk1/apt_archive ./ Packages [766 B]
Ign:4 file:/build/pdf.js-bb4Agq/resolver-zhpIk1/apt_archive ./ Packages
Get:4 file:/build/pdf.js-bb4Agq/resolver-zhpIk1/apt_archive ./ Packages [1374 B]
Get:5 http://incoming.debian.org/debian-buildd buildd-unstable InRelease [39.7 
kB]
Get:6 http://incoming.debian.org/debian-buildd buildd-experimental InRelease 
[39.8 kB]
Get:7 http://incoming.debian.org/debian-buildd buildd-unstable/main amd64 
Packages [137 kB]
Get:8 http://incoming.debian.org/debian-buildd buildd-experimental/main amd64 
Packages [18.5 kB]
Get:9 http://deb.debian.org/debian unstable InRelease [153 kB]
Get:10 http://deb.debian.org/debian experimental InRelease [75.4 kB]
Get:11 http://deb.debian.org/debian unstable/main Sources.diff/Index [27.9 kB]
Get:12 http://deb.debian.org/debian unstable/main amd64 Packages.diff/Index 
[27.9 kB]
Get:13 http://deb.debian.org/debian unstable/main Sources 
2020-12-19-2000.40.pdiff [14.6 kB]
Get:14 http://deb.debian.org/debian unstable/main Sources 
2020-12-20-0200.23.pdiff [11.2 kB]
Get:15 http://deb.debian.org/debian unstable/main Sources 
2020-12-20-0800.26.pdiff [5318 B]
Get:15 http://deb.debian.org/debian unstable/main Sources 
2020-12-20-0800.26.pdiff [5318 B]
Get:16 http://deb.debian.org/debian unstable/main amd64 Packages 
2020-12-19-2000.40.pdiff [45.6 kB]
Get:17 http://deb.debian.org/debian unstable/main amd64 Packages 
2020-12-20-0200.23.pdiff [10.9 kB]
Get:18 http://deb.debian.org/debian unstable/main amd64 Packages 
2020-12-20-0800.26.pdiff [4323 B]
Get:18 http://deb.debian.org/debian unstable/main amd64 Packages 
2020-12-20-0800.26.pdiff [4323 B]
Get:19 http://deb.debian.org/debian experimental/main amd64 Packages [410 kB]
Fetched 1022 kB in 7s (147 kB/s)
Reading package lists...
Reading package lists...
Building dependency tree...
Reading 

[Pkg-javascript-devel] Bug#977781: Bug#977781: real issue is, it does not pull not-yet-cached modules

[Pirate Praveen]

On Mon, 21 Dec 2020 14:24:57 +0530 Pirate Praveen 
 wrote:
> >I think the real issue is that it does not pull not-yet-cached 
modules.

>
> I think the failure is after it downloaded. I can see some files in 
~/.cache/yarn created after it is cleaned after yarnpkg add. Could it 
be a problem with extracting the tar ?


You were correct, these are empty directories, so the failure seems to 
be in downloading.


$ ls ~/.cache/yarn/v6/
npm-d3-color-2.0.0-8d625cab42ed9b8f601a1760a389f7ea9189d62e-integrity
pravi@mahishi:/tmp$ rm -rf ~/.cache/yarn/v6/
pravi@mahishi:/tmp$ yarnpkg add d3-color
yarn add v1.22.10
info No lockfile found.
[1/4] Resolving packages...
[2/4] Fetching packages...
[-] 0/1pravi@mahishi:/tmp$ ls ~/.cache/yarn/v6/
npm-d3-color-2.0.0-8d625cab42ed9b8f601a1760a389f7ea9189d62e-integrity
pravi@mahishi:/tmp$ ls 
~/.cache/yarn/v6/npm-d3-color-2.0.0-8d625cab42ed9b8f601a1760a389f7ea9189d62e-integrity/

node_modules
pravi@mahishi:/tmp$ ls 
~/.cache/yarn/v6/npm-d3-color-2.0.0-8d625cab42ed9b8f601a1760a389f7ea9189d62e-integrity/node_modules/

d3-color
pravi@mahishi:/tmp$ ls 
~/.cache/yarn/v6/npm-d3-color-2.0.0-8d625cab42ed9b8f601a1760a389f7ea9189d62e-integrity/node_modules/d3-color/

pravi@mahishi:/tmp$

--
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#862887: 14 tests fail gulp

[Pirate Praveen]

Control: fixed -1 4.0.2-1

On Fri, 31 May 2019 17:14:12 +0530 Pirate Praveen 
 wrote:
> I'm updating gulp to 4.x and planning to upload it to experimental 
soon.

>
> I have updated node-vinyl-fs in experimental and glob-watcher is
> embedded. The tests are still failing.

Fixed in an earlier upload.

--
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#977535: Bug#977535: Bug#977535: Bug#977535: pkg-js-tools should create node_modules symlink in autopkgtest

[Pirate Praveen]

On Wed, Dec 16, 2020 at 1:38 pm, Xavier  wrote:

Your test modules are not built:

$ node -e 'require("./debian/tests/test_modules/topojson-client")'
internal/modules/cjs/loader.js:323
  throw err;
  ^

Error: Cannot find module
'<...>/node-d3-geo/debian/tests/test_modules/topojson-client/dist/topojson-client.js'.
Please verify that the package.json has a valid "main" entry


That is some problem with ruby-team/meta/build which I also got. But 
directly running sbuild works without this error.


--
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#977535: Bug#977535: Bug#977535: Bug#977535: Bug#977535: pkg-js-tools should create node_modules symlink in autopkgtest

[Pirate Praveen]

On 2020, ഡിസംബർ 16 8:28:01 PM IST, Xavier  wrote:
>
>autopkgtest will be fixed with node-tape migration
>

Thanks for the fix.
-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.

-- 
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#977535: Bug#977535: Bug#977535: Bug#977535: pkg-js-tools should create node_modules symlink in autopkgtest

[Pirate Praveen]

On Wed, Dec 16, 2020 at 1:55 pm, Xavier  wrote:

No, this fails with an sbuild, except with nocheck of course.


It built fine for me as well as on the official buildd normally 
(without enabling nocheck).


See official build logs 
https://buildd.debian.org/status/fetch.php?pkg=node-d3-geo=all=1.11.9-2=1608048295=0


--
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#977535: Bug#977535: Bug#977535: Bug#977535: pkg-js-tools should create node_modules symlink in autopkgtest

[Pirate Praveen]

On 2020, ഡിസംബർ 16 6:45:06 PM IST, Xavier  wrote:
>import tape from "tape";
>^^
>
>SyntaxError: Cannot use import statement outside a module

We need .babelrc too.

https://salsa.debian.org/js-team/node-d3-geo/-/blob/master/debian/patches/use-babel-register-for-esm.patch

-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.

-- 
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#977781: Bug#977781: Bug#977781: Bug#977781: real issue is, it does not pull not-yet-cached modules

[Pirate Praveen]

Control: tags -1 pending

On Tue, Dec 22, 2020 at 1:20 pm, Akshay S Dinesh  
wrote:



   gbp:error: upstream/1.22.10+_cs18.39.16 is not a valid treeish

indeed your fork only has 33 tags, whereas js-team/node-yarnpkg has 
37.
Please pull those tags and push them to your fork, then force 
restart the CI pipeline.

This would help us to see if your proposed fix works.


Pushing tags indeed helped extract sources. But build fails due to 
incompatibilities with upstream files




As to upgrading tar-fs, it is possible that some other dependency we 
updated here and there requires it.

Upstream are currently using 1.16.3:
https://github.com/yarnpkg/yarn/blob/master/yarn.lock#L7137
whereas we were already using version 2

If we want to upgrade tar-fs we need to upgrade its sources and then 
import them in upstream and master branches:

https://wiki.debian.org/Javascript/GroupSourcesTutorial



I think Praveen locked the dependency on tar-fs to version 1.x in 
https://salsa.debian.org/js-team/node-yarnpkg/-/commit/8f44f7d238f4330b89d3b62c2cc369bb909459a6


I'm unsure if that's because upstream yarn mentions 1.x tar-fs as 
dependency or because there are other dependencies to 1.x tar-fs.


The API of tar-fs doesn't change between 1.x and 2.x, but the 
dependencies do. And the dependencies we have in debian make it such 
that 1.x doesn't work.


I tried following GroupSourcesTutorial and gbp manual. It is becoming 
very confusing for me with many version numbers and tags floating 
around. So I'll have to leave this here for possibly Praveen to pick 
up.


To update a component, you have to update debian/watch and run uscan, 
then gbp import orig --pristine-tar.


- 
https://registry.npmjs.org/tar-fs/-/tar-fs-(1(?:.[\d\.]+)?)@ARCHIVE_EXT@ 
checksum
+ 
https://registry.npmjs.org/tar-fs/-/tar-fs-(2(?:.[\d\.]+)?)@ARCHIVE_EXT@ 
checksum


But it seems ctype=nodejs is not working as expected (it is supposed to 
download versions matching with package.json but that does not seem to 
be working).


I can install packages now. Uploading the fixed version.

--
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#977304: autosize.js: include add-module-exports plugin equivalent in .babelrc

[Pirate Praveen]

Package: autosize.js
Version: 4.0.2~dfsg1-4
Severity: important

I get this error is javascript console when running gitlab,

TypeError: a() is not a function. (In 'a()(this.textarea)', 'a()' is an 
instance of Object)


It seems to be generated by this code,

document.addEventListener("DOMContentLoaded", function() {
   Object(s.a)(function() {
   const t = document.querySelectorAll(".js-autosize");
   a()(t),
   a.a.update(t),
   t.forEach(function(t) {
   return t.classList.add("js-autosize-initialized")
   })
   })
   });

I suspect this is caused by autosize.js build issues

https://salsa.debian.org/js-team/autosize.js/-/blob/master/debian/patches/add-babelrc.patch 
tries to replace some babel 6 modules with babel 7 equivalents.


But is it not include add-module-exports plugin 
https://salsa.debian.org/js-team/autosize.js/-/blob/master/build.js#L51


I think we should add this plugin also to babelrc and add 
node-babel-plugin-add-module-exports as build dependency.


--
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#977269: Bug#977269: node-rollup-plugin-terser seems incompatible with current node-terser

[Pirate Praveen]

On Sun, Dec 13, 2020 at 1:19 pm, Xavier Guimard  wrote:

Package: node-rollup-plugin-terser
Version: 7.0.2-2
Severity: grave
Justification: renders package unusable

When trying current rollup-plugin-terser (7.0.2)  with current
node-terser (4.1.2), package is unuseable:

$ rollup -c

index.js → dist/pako.js, dist/pako.min.js...
[!] (plugin terser) Error: Cannot find module 
'/home/xavier/dev/debian/src/pkg-js/packages/node-pako/node_modules/terser/dist/bundle.min.js'. 
Please verify that the package.json has a valid "main" entry
Error: Cannot find module 
'/home/xavier/dev/debian/src/pkg-js/packages/node-pako/node_modules/terser/dist/bundle.min.js'.


There is a possibility that this is caused by symbolic links.

I'm hit by symbolic link issue with yarn so I suspect this could be the 
case here too.


Try adding a custom path to node-resolve plugin instead of adding a 
symbolic link


see this example
https://salsa.debian.org/js-team/node-chart.js/commit/979576e93b7aa17083ae5149e9753a5f6b1a522d

--
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#977781: yarnpkg: fails to download modules

[Pirate Praveen]

Package: yarnpkg
Version: 1.22.10+~cs18.39.16-1
Severity: serious

Since yarnpkg add command did not return an error, the autpkgtest was 
succeeding even though it did not add any modules to node_modules 
directory.


I have fixed the faulty autopkgtest which now exposes the failure.

--
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#977781: Bug#977781: yarnpkg: fails to download modules

[Pirate Praveen]

On Mon, Dec 21, 2020 at 1:37 am, Pirate Praveen 
 wrote:
On Mon, 21 Dec 2020 00:39:35 +0530 Pirate Praveen 
 wrote:
> Since yarnpkg add command did not return an error, the autpkgtest 
was

> succeeding even though it did not add any modules to node_modules
> directory.

Though this is sufficient to install yarn 2 (berry).

$ yarnpkg set version berry
Resolving berry to a url...
Downloading 
https://github.com/yarnpkg/berry/raw/master/packages/berry-cli/bin/berry.js..

Saving it into /tmp/project1/.yarn/releases/yarn-berry.cjs...
Updating /tmp/project1/.yarnrc.yml...
Done!

$ yarnpkg init
{
 name: 'project1'
}
pravi@mahishi:/tmp/project1$ ls
package.json README.md yarn.lock
pravi@mahishi:/tmp/project1$ yarnpkg add d3-color
➤ YN: ┌ Resolution step
➤ YN: └ Completed
➤ YN: ┌ Fetch step
➤ YN0013: │ d3-color@npm:2.0.0 can't be found in the cache and 
will be fetched from

➤ YN: └ Completed in 0s 735ms
➤ YN: ┌ Link step
➤ YN: └ Completed
➤ YN: Done in 0s 797ms
$ ls .yarn/cache/
d3-color-npm-2.0.0-e7f04a5d87-637e111598.zip
gitignore


We need to create ~/.yarnrc.yml to create node_modules directory.

$ cat ~/.yarnrc.yml
nodeLinker: "node-modules"

$ yarnpkg install
\➤ YN: ┌ Resolution step
➤ YN: └ Completed
➤ YN: ┌ Fetch step
➤ YN: └ Completed
➤ YN: ┌ Link step
➤ YN: └ Completed
➤ YN: Done in 0s 203ms
pravi@mahishi:/tmp/project1$ ls
node_modules  package.json  README.md  yarn.lock
pravi@mahishi:/tmp/project1$ ls node_modules/
d3-color
pravi@mahishi:/tmp/project1$ ls node_modules/d3-color/
dist  LICENSE  package.json  README.md  src

--
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#977781: Bug#977781: Bug#977781: yarnpkg: fails to download modules

[Pirate Praveen]

On Mon, Dec 21, 2020 at 1:46 am, Pirate Praveen 
 wrote:

We need to create ~/.yarnrc.yml to create node_modules directory.

$ cat ~/.yarnrc.yml
nodeLinker: "node-modules"

$ yarnpkg install
\➤ YN: ┌ Resolution step
➤ YN: └ Completed
➤ YN: ┌ Fetch step
➤ YN: └ Completed
➤ YN: ┌ Link step
➤ YN: └ Completed
➤ YN: Done in 0s 203ms
pravi@mahishi:/tmp/project1$ ls
node_modules  package.json  README.md  yarn.lock
pravi@mahishi:/tmp/project1$ ls node_modules/
d3-color
pravi@mahishi:/tmp/project1$ ls node_modules/d3-color/
dist  LICENSE  package.json  README.md  src

In the worst case scenario if we cannot get this working, we can 
document how to setup yarn 2 using the package instead of dropping this 
from bullseye.


We may have to update description and move to contrib in that case. We 
can at least built this in bullseye, which is an improvement from the 
earlier state where we had to use snapshot.debian.org to build and 
bootstrap.


--
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#977781: yarnpkg: fails to download modules

[Pirate Praveen]

On Mon, 21 Dec 2020 00:39:35 +0530 Pirate Praveen 
 wrote:

> Since yarnpkg add command did not return an error, the autpkgtest was
> succeeding even though it did not add any modules to node_modules
> directory.

Though this is sufficient to install yarn 2 (berry).

$ yarnpkg set version berry
Resolving berry to a url...
Downloading 
https://github.com/yarnpkg/berry/raw/master/packages/berry-cli/bin/berry.js..

Saving it into /tmp/project1/.yarn/releases/yarn-berry.cjs...
Updating /tmp/project1/.yarnrc.yml...
Done!

$ yarnpkg init
{
 name: 'project1'
}
pravi@mahishi:/tmp/project1$ ls
package.json README.md yarn.lock
pravi@mahishi:/tmp/project1$ yarnpkg add d3-color
➤ YN: ┌ Resolution step
➤ YN: └ Completed
➤ YN: ┌ Fetch step
➤ YN0013: │ d3-color@npm:2.0.0 can't be found in the cache and will 
be fetched from

➤ YN: └ Completed in 0s 735ms
➤ YN: ┌ Link step
➤ YN: └ Completed
➤ YN: Done in 0s 797ms
$ ls .yarn/cache/
d3-color-npm-2.0.0-e7f04a5d87-637e111598.zip
gitignore

--
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#973741: Bug#973741: gitlab: Yarn hasn't been able to find a cache folder it can use

[Pirate Praveen]

On Thu, Nov 19, 2020 at 18:58, Xavier  wrote:

we opened bugs to upstream repo and are waiting for...


I don't think upstream will make any significant changes to 1.x branch 
any more. Someone who want to see yarn in debian bullseye will have to 
fix it.


--
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#973741: gitlab: Yarn hasn't been able to find a cache folder it can use

[Pirate Praveen]

On 2020, നവംബർ 19 11:01:11 PM IST, Michael Prokop  wrote:
>Hi,
>
>* Pirate Praveen [Thu Nov 19, 2020 at 03:05:13PM +0530]:
>
>> As you already found out, the problem is in node-yarnpkg. The fix is
>> a bit hard though as node-yarnpkg currently ftbfs due to babel 7
>> transition.
>
>> A work around could be to install yarnpkg via npm. npm install -g
>> yarn and replace the yarnpkg command.
>
>I noticed that yarnpkg currently isn't part of Debian/testing
>(according to https://tracker.debian.org/pkg/node-yarnpkg due to
>"Updating node-yarnpkg introduces new bugs: #960120, #972952, #973741").
>
>It would be rather unfortunate if it wouldn't make it into bullseye.
>Sadly I can't really help with the mentioned bugreports myself, but is
>there a chance, to see yarnpkg back in Debian/testing (given that
>latest interaction in e.g. #960120 dates back to August) so it could
>make it into bullseye? :)

I can see 2 possibilities,

1. Someone make yarn 1.x build with babel 7
2. Yarn 2.x gets a stable release and it is updated

I'm not sure if either of it will happen in time for bullseye. I tried my best 
with option 1, but I'm not a js programmer to unblock it. I asked a few people 
for help, but was not successful in that attempt.

-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.

-- 
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#974069: Bug#974069: error Yarn hasn't been able to find a cache folder it can use although folders are writable

[Pirate Praveen]

On 2020, നവംബർ 9 9:13:58 PM IST, Daniel Leidert  wrote:
>Package: yarnpkg
>Version: 1.22.4-3
>Severity: important
>
>-BEGIN PGP SIGNED MESSAGE-
>Hash: SHA512
>
>I'm running `rails new ...`. At the end I get this:
>
>[..]
>Installing all JavaScript dependencies [4.2.2]
> run  yarnpkg add @rails/webpacker@4.2.2 from "."
>yarn add v1.22.4
>warning Skipping preferred cache folder "/home/daniel/.cache/yarn" because it 
>is not writable.
>warning Skipping preferred cache folder "/tmp/.yarn-cache-1000" because it is 
>not writable.
>warning Skipping preferred cache folder "/tmp/.yarn-cache" because it is not 
>writable.
>error Yarn hasn't been able to find a cache folder it can use. Please use the 
>explicit --cache-folder option to tell it what location to use, or make one of 
>the preferred locations writable.
>info Visit https://yarnpkg.com/en/docs/cli/add for documentation about this 
>command.
>Installing dev server for live reloading
> run  yarnpkg add --dev webpack-dev-server from "."
>yarn add v1.22.4
>warning Skipping preferred cache folder "/home/daniel/.cache/yarn" because it 
>is not writable.
>warning Skipping preferred cache folder "/tmp/.yarn-cache-1000" because it is 
>not writable.
>warning Skipping preferred cache folder "/tmp/.yarn-cache" because it is not 
>writable.
>error Yarn hasn't been able to find a cache folder it can use. Please use the 
>explicit --cache-folder option to tell it what location to use, or make one of 
>the preferred locations writable.
>info Visit https://yarnpkg.com/en/docs/cli/add for documentation about this 
>command.
>
>The folders are writable. I even tried to make /home/daniel/.cache/yarn
>world-writeable. This seems odd.
>

This is caused by node-mkdirp transition, but node-yarnpkg is ftbfs currently 
(caused by node-babel/node-babel7 transition) which makes it hard to fix.
-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.

-- 
Pkg-javascript-devel mailing list
Pkg-javascript-devel@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel

Re: [Pkg-javascript-devel] use uglify-js 3 when possible, instead of terser

[Pirate Praveen]

On Fri, Nov 6, 2020 at 11:26, Jonas Smedegaard  wrote:

I recommend to use uglify-js 3 instead of terser, when possible.

 * Terser can minify modern code (uglify-js 3 only ES5).
 * Uglify-js 3 needs 3 nodejs packages to build (terser needs 134).
 * Uglify-js 3 package is up-to-date (terser is 16 months behind).

Therefore, for code that is written as or transpiled to ES5, better 
use

uglify-js 3 to minify it: Your package then a) gets minified using
newest upstream knowledge, and b) reduces risk of getting caught in 
in a

larger package migration.

Specifically, do *not* casually switch a package from uglify-js 3 to
terser when helping out others in the JavaScript team: Please ask 
first.


(avoid uglifyjs 2, however: It is ancient and unmaintained code!)


Though with more and more browsers supporting ES6 features natively, 
transpiling to ES5 may not be necessary for many packages. If we have 
to maintain terser anyway and it being a superset of uglifyjs, I don't 
see the reason for new packages to use uglify-js. But as you requested, 
if some package is using uglify-js already, it may be fine to keept it 
as is. As for breaking things and transitions, I think we need to be 
more careful and plan it 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

Re: [Pkg-javascript-devel] node-postcss 7.x -> 8.x transition - work started in experimental

[Pirate Praveen]

On 2020, ഡിസംബർ 24 8:49:47 PM IST, Pirate Praveen  
wrote:
>
>
>On Mon, Sep 28, 2020 at 8:01 pm, Pirate Praveen 
> wrote:
>> Hi,
>> 
>> I have uploaded node-postcss 8.0.5-1 to experimental.
>> 
>> I have started 
>> https://wiki.debian.org/Javascript/Nodejs/Transitions/PostCSS8 to 
>> track progress of this transition. Help is welcome.
>
>With all reverse dependencies fixed and bug filed against rainloop (on 
>28th Sepetember). I'm going to upload node-postcss 8.x to unstable now. 
>Thanks to yadd for help with the transition.
>

node-postcss-filter-plugins 

node-postcss-minify-font-values 

node-postcss-reporter 

I'm planning to file removal request for these 3 packages. If someone want to 
continue maintaining these, please step in now and fix node-postcss 8 breakage.
-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.

-- 
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#977900: node-autoprefixer: FTBFS: ENOENT: no such file or directory, open 'path'

[Pirate Praveen]

Control: reopen -1

On Thu, 24 Dec 2020 20:44:50 +0530 Pirate Praveen  
wrote:
> It is fixed by changing the order of plugins used in rollup.config.js, 
> rollup-plugin-polyfills should come before commonjs and node-resolve 
> plugins.

Even though the build now succeed, it is producing a broken output. Size of 
autoprefixer.js dropped from 4.5 mb to 900 kb. It should bundle postcss and 
polyfills.

It may be because newer versions of browsers supporting new features without 
polyfills. But we need to confirm it.

One way could be building the upstream code with build dependencies matching 
the versions in debian. rollup, its plugins or caniuse-db/browserslist update 
may have caused this change.

-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.-- 
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#977900: node-autoprefixer: FTBFS: ENOENT: no such file or directory, open 'path'

[Pirate Praveen]

Control: forwarded -1 
https://github.com/ai/autoprefixer-rails/issues/199


On Fri, 25 Dec 2020 14:51:34 +0530 Pirate Praveen 
 wrote:
> Even though the build now succeed, it is producing a broken output. 
Size of autoprefixer.js dropped from 4.5 mb to 900 kb. It should bundle 
postcss and polyfills.

>
> It may be because newer versions of browsers supporting new features 
without polyfills. But we need to confirm it.

>
> One way could be building the upstream code with build dependencies 
matching the versions in debian. rollup, its plugins or 
caniuse-db/browserslist update may have caused this change.


This seems to be caused by @rollup/plugin-node-resolve 10. Running 
build in upstream repo with updated @rollup/plugin-node-resolve throws 
a similar error.


With upsteam yarn.lock and yarnpkg install,

(debian-sid)pravi@ilvala2:~/forge/js-team/autoprefixer-rails-10.1.0.0/build$ 
yarnpkg run rollup -c

yarn run v1.22.10
$ 
/home/pravi/forge/js-team/autoprefixer-rails-10.1.0.0/build/node_modules/.bin/rollup 
-c


autoprefixer.js → ../vendor/autoprefixer.js...
created ../vendor/autoprefixer.js in 8s
Done in 8.47s.

Now with updated @rollup/plugin-node-resolve

(debian-sid)pravi@ilvala2:~/forge/js-team/autoprefixer-rails-10.1.0.0/build$ 
yarnpkg upgrade @rollup/plugin-node-resolve@^10.0.0

yarn upgrade v1.22.10
[1/4] Resolving packages...
[2/4] Fetching packages...
info fsevents@2.1.3: The platform "linux" is incompatible with this 
module.
info "fsevents@2.1.3" is an optional dependency and failed 
compatibility check. Excluding it from installation.

[3/4] Linking dependencies...
[4/4] Rebuilding all packages...
success Saved lockfile.
success Saved 1 new dependency.
info Direct dependencies
└─ @rollup/plugin-node-resolve@10.0.0
info All dependencies
└─ @rollup/plugin-node-resolve@10.0.0
Done in 3.75s.

$ yarnpkg run rollup -c
yarn run v1.22.10
$ 
/home/pravi/forge/js-team/autoprefixer-rails-10.1.0.0/build/node_modules/.bin/rollup 
-c


autoprefixer.js → ../vendor/autoprefixer.js...
[!] Error: Could not load process (imported by 
node_modules/postcss/lib/postcss.js): ENOENT: no such file or 
directory, open 'process'
Error: Could not load process (imported by 
node_modules/postcss/lib/postcss.js): ENOENT: no such file or 
directory, open 'process'


error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about 
this command.


--
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#977796: mocha, node-postcss: both ship usr/share/nodejs/nanoid/*

[Pirate Praveen]

Control: reassign -1 mocha

On Mon, 21 Dec 2020 01:40:48 +0100 Andreas Beckmann  wrote:
> Package: mocha,node-postcss

Fixed in mocha.
-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.-- 
Pkg-javascript-devel mailing list
Pkg-javascript-devel@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel

Re: [Pkg-javascript-devel] Removing legacy rollup-plugin-node-resolve module

[Pirate Praveen]

On Tue, Dec 29, 2020 at 16:52, Jonas Smedegaard  wrote:

Quoting Pirate Praveen (2020-12-29 16:28:17)

 I'd like to remove embedded copy of rollup-plugin-node-resolve from
 bullseye and port all modules to use @rollup/plugin-node-resolve

 I have rebuilt all the reverse dependencies and you can see the list
 of packages that failed at

 
https://wiki.debian.org/Javascript/Nodejs/Transitions/Rollup-plugin-node-resolve-legacy-rm


 Most of the time, just a simple one line change should be enough.

 --- a/rollup.config.js
 +++ b/rollup.config.js
 @@ -1,5 +1,5 @@
  import ascii from "rollup-plugin-ascii";
 -import node from "rollup-plugin-node-resolve";
 +import node from "@rollup/plugin-node-resolve";
  import {terser} from "rollup-plugin-terser";
  import * as meta from "./package.json";


...and then tighten build-dependencies to something like this:

  node-rollup-plugin-node-resolve (>= 9),


More tips are added to the wiki page shared above. With help from Jonas 
and Abraham Raji, we have just 4 more packages to fix. Once current 
version of eslint/node-regexpp in unstable migrates to testing, I will 
upload this version to unstable.




--
Pkg-javascript-devel mailing list
Pkg-javascript-devel@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel

Re: [Pkg-javascript-devel] Removing legacy rollup-plugin-node-resolve module

[Pirate Praveen]

On Thu, Dec 31, 2020 at 18:21, Pirate Praveen 
 wrote:
More tips are added to the wiki page shared above. With help from 
Jonas and Abraham Raji, we have just 4 more packages to fix. Once 
current version of eslint/node-regexpp in unstable migrates to 
testing, I will upload this version to unstable.


With node-rollup-plugin-node-resolve 11, the syntax we use to add 
/usr/share/nodejs to resolve path has changed.


See 
https://wiki.debian.org/Javascript/Nodejs/Transitions/Rollup-plugin-node-resolve-11 
for how to replace the deprecated option and affected packages. Help is 
welcome.




--
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] Removing legacy rollup-plugin-babel

[Pirate Praveen]

Hi,

With removal of legacy embedded rollup-plugin-node-resolve completed, 
I'd like to remove legacy rollup-plugin-babel now


List of packages that fail rebuild is given at
https://wiki.debian.org/Javascript/Nodejs/Transitions/Rollup-plugin-babel-rm

Help is welcome.

Thanks
Praveen



--
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] Removing legacy rollup-plugin-json component for bullseye

[Pirate Praveen]

Hi,

Continuing the rollup plugins cleanup effort, I have rebuilt packages 
that build depend on node-rollup-plugin-json and found a few that needs 
fixing.


Details in the wiki page,
https://wiki.debian.org/Javascript/Nodejs/Transitions/Rollup-plugin-json-legacy-rm

Help welcome.

Thanks
Praveen



--
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#979157: node-rollup-plugin-json: drop legacy plugin component

[Pirate Praveen]

Package: node-rollup-plugin-json
Version: 4.1.0+repack+~4.0.0-2
Severity: important
Owner: Pirate Praveen 

To reduce the maintenance burden, I plan to remove the legacy component 
from this package similar to earlier transitions done for node-resolve, 
babel, commonjs and alias plugins.


--
Pkg-javascript-devel mailing list
Pkg-javascript-devel@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel

Re: [Pkg-javascript-devel] Yarnpkg future

[Pirate Praveen]

On Mon, Jan 4, 2021 at 12:27 pm, Paolo Greppi  
wrote:
The good news of 2020 was the successful team effort (thanks again 
Akshay S Dinesh and Pirate Praveen !) to keep yarnpkg in bullseye.


Tha bad news of 2021 has been these issues being closed by upstream:
https://github.com/yarnpkg/yarn/issues/8081
https://github.com/yarnpkg/yarn/issues/8083
https://github.com/yarnpkg/yarn/issues/8417

So yarn2 is the future, but yarn1 is still required to “install” 
it.
More precisely to "vendor" it, i.e. to install in each repo a copy of 
the package manager binary compatible with the package.json / 
yarn.lock dialect or mode or flavor that particular repo is using.


If this sounds crazy, read these issues on the yarn2 (“berry”) 
upstream:

https://github.com/yarnpkg/berry/issues/181
https://github.com/yarnpkg/berry/issues/2216

As it has been in the last 25 years, the JavaScript ecosystem is a 
moving target (besides yarn2’s pnp mode there is pnpm and deno 
(https://bugs.debian.org/961337) ...) and it does not help to be 
ideological.
From Debian (or any distribution) POV it’s OK if users choose to 
use the tools we provide in suicidal ways (piping curl into sudo 
bash, depending on registries and binary downloads for each and every 
build, vendoring binaries etc.).

We all do, by the way !

Our only concern should be to also make it possible to use these same 
tools in a sane way, for example making it possible (at some point in 
the future) to reproducibly build a signal-desktop 
(https://bugs.debian.org/842943) binary from clearly identified 
sources and without network access. Ah, and of course maintaining all 
that in the mid term.


I propose that as js-team we open a single issue on the yarn2 
(“berry”) repo, with the request to drop yarn1 and to support 
yarn2 as the only globally installed yarnpkg version on the system.
In that case if I init a new “yarn2” repo with my global yarn2 
binary, it does not need to vendor itself.
But it would vendor yarn1 if you have a legacy repo. Of vendor yarn3 
if you want to use yarn-next.
When yarn3 becomes stable, upgrade the globally installed yarnpkg 
version to that and so on.




That sounds good to me. Go ahead and ask. Though I'm not sure if they 
will be open to it, but no harm in asking.


Debian’s baseline task would be to only support the current stable 
yarnpkg version (yes, that will be fun for “berry” see: 
https://bugs.debian.org/976081#63).
And supporting the oldstable version (as we’re doing with yarn1 in 
bullseye) only if required.


What do you think ?


Looks good to me.



--
Pkg-javascript-devel mailing list
Pkg-javascript-devel@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel

Re: [Pkg-javascript-devel] Yarnpkg future

[Pirate Praveen]

On Tue, Jan 5, 2021 at 9:50 pm, Pirate Praveen 
 wrote:
That sounds good to me. Go ahead and ask. Though I'm not sure if they 
will be open to it, but no harm in asking.


They seem to support building yarn 2 directly via corepack

https://github.com/yarnpkg/yarn/issues/8083#issuecomment-754768675

We will have to use git master and exclude .yarn/cache from the tar and 
try building with webpack.


On a first look, this seems doable.



--
Pkg-javascript-devel mailing list
Pkg-javascript-devel@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel

Re: [Pkg-javascript-devel] Yarnpkg future

[Pirate Praveen]

On Wed, Jan 6, 2021 at 2:48 pm, Pirate Praveen 
 wrote:



On Tue, Jan 5, 2021 at 9:50 pm, Pirate Praveen 
 wrote:
That sounds good to me. Go ahead and ask. Though I'm not sure if 
they will be open to it, but no harm in asking.


They seem to support building yarn 2 directly via corepack

https://github.com/yarnpkg/yarn/issues/8083#issuecomment-754768675

We will have to use git master and exclude .yarn/cache from the tar 
and try building with webpack.


On a first look, this seems doable.

I'm trying to build corepack and it is progressing well. We will need 
to package some dependencies (clipanion, terser-webpack-plugin, 
ts-loader etc). I will report how it goes as I make progress.




--
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#979551: Bug#979551: node-babel7: update-alternatives set up fails

[Pirate Praveen]

On 2021, ജനുവരി 8 1:16:36 PM IST, Paolo Greppi  wrote:
>BTW, why is node-babel7 a run-time dependency of yarnpkg ?
>Should it not just be a build-dep ?
>

It needs @babel/runtime which is currently part of node-babel7. I think yadd 
already uploaded a version of node-babel7 with separate node-babel7-runtime 
binary package. But it has not cleared NEW yet.

-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.

-- 
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#979551: Bug#979551: Bug#979551: node-babel7: update-alternatives set up fails

[Pirate Praveen]

On Fri, Jan 8, 2021 at 12:06 pm, Jonas Smedegaard  
wrote:

Quoting Pirate Praveen (2021-01-08 11:55:14)



 On 2021, ജനുവരി 8 1:16:36 PM IST, Paolo Greppi 
 wrote:

 >BTW, why is node-babel7 a run-time dependency of yarnpkg ?
 >Should it not just be a build-dep ?
 >

 It needs @babel/runtime which is currently part of node-babel7. I 
think yadd already uploaded a version of node-babel7 with separate 
node-babel7-runtime binary package. But it has not cleared NEW yet.


You need not wait for NEW clearance to depend explicitly on required
packages - you need only have the required packages available as 
virtual

packages.



Yes, but changing dependency alone will not solve this issue. When it 
clears NEW and dependency is updated, this bug will be fixed for 
yarnpkg, but node-babel7 will still be affected.


--
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#979531: lodash/fp does not have all the files shipped by npm dist.tarball

[Pirate Praveen]

Control: forwarded -1 https://github.com/lodash/lodash/issues/5051

Even upstream build is broken.

yarnpkg build:fp-modules is also generating only 104 files.

--
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#979551: Bug#979551: Bug#979551: node-babel7: update-alternatives set up fails

[Pirate Praveen]

On Fri, Jan 8, 2021 at 12:44 pm, Jonas Smedegaard  
wrote:
I don't understand - how is node-babel7 affected by how yarnpkg 
declares

(build-)dependencies against it?



node-babel7 will still be affected by the update-alternatives bug when 
manpages missing.


What I suggest is to improve the package yarnpkg to replace any 
runtime

and build-time package relations on node-babel7 to instead be on each
actually needed node-$module package, virtual or not.

(and yes, it should work fine for autopkgtest as well - a previous
failure I caused was due to lack of appending (>= 7) for a virtual
package also provided by older babel6 package).


That is tangential to this particular bug. That is an improvement, yes, 
but will not solve this bug without separate binary for @babel/runtime 
module, as it will still pull in node-babel7 and missing man pages will 
trigger this bug.


--
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#980406: Bug#980406: This is confirmed as a bug in debian package

[Pirate Praveen]

On Tue, Jan 19, 2021 at 2:24 pm, Pirate Praveen 
 wrote:

Control: severity -1 serious

I was able to use xterm 3.8.1 from nmpjs.com with gitlab without any 
issues. So this is a bug in node-xterm debian build.


Trying to switch to rollup instead of browserify-lite, but tsc itself 
is failing now.


diff --git a/debian/control b/debian/control
index 6bc5004..f70533d 100644
--- a/debian/control
+++ b/debian/control
@@ -7,9 +7,12 @@ Priority: optional
Build-Depends: chai ,
   debhelper-compat (= 12),
   mocha ,
-   node-browserify-lite,
+   rollup,
   node-typescript,
   node-typescript-types (>= 20190609~),
+   node-types-jquery,
+   node-types-jsdom,
+   node-types-mocha,
   nodejs,
   pkg-js-tools
Standards-Version: 4.5.0
diff --git a/debian/rules b/debian/rules
index d8dcc53..72fc167 100755
--- a/debian/rules
+++ b/debian/rules
@@ -17,17 +17,8 @@ override_dh_auto_build:
# Otherwise browserify-lite complains
touch lib/addons/index.js
mkdir -p dist
-	cd dist && browserify-lite ../lib/xterm.js --outfile xterm.js 
--standalone Terminal
-	cd dist && for addon in $(ADDONS); do mkdir -p addons/$$addon && 
browserify-lite ../lib/addons/$$addon/$$addon.js --outfile 
addons/$$addon/$$addon.js --standalone $$addon; done

-# Undo browserify-lite workarounds
-	sed -i -e 's/REQUIRE_NO_BROWSERIFY/require/g' dist/xterm.js 
dist/addons/*/*.js
-# browserify-lite seems to generate a module map with indexes starting 
from zero, then tests
-# the truth of the module ID when loading sub-parts - which then fails 
for whatever ends up
-# as sub-module 0; not convinced I fully understand what is happening 
here, because it seems
-# like this should break everything browserify-life produces; dropping 
this check makes it load;
-	sed -i -e '/if [(]!id[)] throw new Error/d' dist/xterm.js 
dist/addons/*/*.js

-
-   rm -f dist/addons/index.js
+   cd dist && rollup ../lib/xterm.js -o xterm.js -f umd -name Terminal
+	cd dist && for addon in $(ADDONS); do mkdir -p addons/$$addon && 
rollup ../lib/addons/$$addon/$$addon.js -o addons/$$addon/$$addon.js -f 
umd -name $$addon; done

cd src && find . -name '*.css' -exec cp -v --parents '{}' ../lib \;
cd src && find . -name '*.css' -exec cp -v --parents '{}' ../dist \;

--
Pkg-javascript-devel mailing list
Pkg-javascript-devel@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel

Re: [Pkg-javascript-devel] node-buble_0.20.0+~0.19.2-1~bpo10+2_amd64.changes ACCEPTED into buster-backports

[Pirate Praveen]

On 2021, ജനുവരി 14 8:26:55 PM IST, Jonas Smedegaard  wrote:
>> That is not the case here, as node-acorn (>= 6~) cannot be satisfied 
>> by the real package node-acorn 5.5.3
>
>Sounds like you know with great confidence (so I will refrain from 
>sharing my additional related theories here, to not annoy you further).
>

I have seen this bug before and analyzed the situation before as well.

>> > Try tighten (build-)dependencies to only possibly match the virtual 
>> > package.
>> > 
>> 
>> That is already done.
>
>Interesting.  Then it sounds like a bug in the infrastructure.
>
>
>> > That should lead to the virtual package getting installed.
>> > 
>> 
>> No it does not, you can try it yourself if you don't believe me.
>
>I believe you, and I am confident that you are doing the best that you 
>can (and that "the best that you can" is quite good).
>
>That said, I do not expect you to be an all-knowing deity (sorry), and 
>am sharing what as I understand it is the expected behavior of Debian 
>infrastructure - not directly to say "you are doing it wrong" but 
>slightly more vaguely aid in moving this issue forward, e.g. through 
>"oh, I didn't know that detail" or "sure, I know that and that can 
>definitely be ruled out as a cause".
>
>Hope that is acceptable clarification.

That is fine.

>
>> > If it leads to no package being resolved or the unacceptably 
>> > versioned real package getting resolved, then file a severe bug 
>> > against the resoilver or build environment.
>> 
>> I don't know if that can be a severe bug. But reported against 
>> aptitude and aspcud now.
>
>Good.
>
>If you share bug numbers here it may encourage some reading this to 
>contribute to solving those bugs.  If that was the case already when you 
>wrote the changelog entry, then for future sake you can consider a "(see 
>bug#123456)" notice to such changelog antry for the same reason: steer 
>potential help towards where they do most good instead of bothering busy 
>developers with silly questions about things already well understood and 
>ruled out.

I opened this bug now and since it affects buster it is unlikely to be part of 
a buster update, even if we fix these tools in sid/bullseye.

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=980099.

>Thanks for taking the time to share these details.
>
>
> - Jonas
>

-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.

-- 
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] A tutorial explaining common but complicated cases when maintaining javascript packages

[Pirate Praveen]

Hi JS team,

You can see the tutorial here,
https://wiki.debian.org/Javascript/Nodejs/Npm2Deb/AdvancedTutorial

I have also included video demo for each of the steps. Feel free to 
improve/contribute more explanations.


Thanks
Praveen



--
Pkg-javascript-devel mailing list
Pkg-javascript-devel@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel

Re: [Pkg-javascript-devel] Replace 'yui-compressor' with 'uglifyjs'

[Pirate Praveen]

On Mon, Jan 18, 2021 at 9:23 am, Xavier  wrote:

+1, but we have to find a replacement for CSS files: uglifyjs can't
manage them while yui-compressor can.


cleancss can minify css



--
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#980406: Bug#980406: marked as done (node-xterm: likely broken build - JSON.parse: unexpected character at line 1 column 1 of the JSON data Resource)

[Pirate Praveen]

Control: reopen -1
Control: severity -1 important
Control: tags -1 help

On Tue, Jan 19, 2021 at 6:54 pm, Debian Bug Tracking System 
 wrote:

Your message dated Tue, 19 Jan 2021 18:50:13 +
with message-id 
and subject line Bug#980406: fixed in node-xterm 3.8.1+~cs0.9.0-1
has caused the Debian Bug report #980406,
regarding node-xterm: likely broken build - JSON.parse: unexpected 
character at line 1 column 1 of the JSON data Resource

to be marked as done.


I was testing with a wrong version of xterm. So reopening with a lower 
severity. gitlab should not be using the browser bundle but the node 
modules. Its probably the files that are not built that is causing the 
error.


Need help with building node-pty component, which would enable us to 
build src/Terminal.integration.ts


--
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#980406: Bug#980406: Bug#980406: This is confirmed as a bug in debian package

[Pirate Praveen]

On Tue, Jan 19, 2021 at 5:06 pm, Xavier  wrote:

Le 19/01/2021 à 15:04, Pirate Praveen a écrit :



 On Tue, Jan 19, 2021 at 2:24 pm, Pirate Praveen
  wrote:

 Control: severity -1 serious

 I was able to use xterm 3.8.1 from nmpjs.com with gitlab without 
any

 issues. So this is a bug in node-xterm debian build.


 Trying to switch to rollup instead of browserify-lite, but tsc 
itself is

 failing now.


--- a/src/Terminal.ts
+++ b/src/Terminal.ts
@@ -1636,7 +1636,9 @@
*/
   public log(text: string, data?: any): void {
 if (!this.options.debug) return;
+// @ts-ignore
 if (!this._context.console || !this._context.console.log) return;
+// @ts-ignore
 this._context.console.log(text, data);
   }

@@ -1645,7 +1647,9 @@
*/
   public error(text: string, data?: any): void {
 if (!this.options.debug) return;
+// @ts-ignore
 if (!this._context.console || !this._context.console.error) 
return;

+// @ts-ignore
 this._context.console.error(text, data);
   }

--- a/src/renderer/ColorManager.test.ts
+++ b/src/renderer/ColorManager.test.ts
@@ -15,6 +15,7 @@

   beforeEach(() => {
 dom = new jsdom.JSDOM('');
+// @ts-ignore
 window = dom.window;
 document = window.document;
 (window).HTMLCanvasElement.prototype.getContext = () => ({


I don't really understand this part. Can you fix this?

thanks
Praveen

--
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#980406: node-xterm: likely broken build - JSON.parse: unexpected character at line 1 column 1 of the JSON data Resource

[Pirate Praveen]

Package: node-xterm
Version: 3.8.1-4
Severity: important

When using packaged version of node-xterm in gitlab, the browser error 
console has these errors and it break web IDE of gitlab (the progress 
circle keeps spinning).


Source map error: Error: JSON.parse: unexpected character at line 1 
column 1 of the JSON data Resource URL: 
http://gitlab-buster.lxc/assets/webpack/commons-pages.ide-pages.projects.environments.terminal-pages.projects.jobs.terminal.650166e5.chunk.js 
Source Map URL: 
commons-pages.ide-pages.projects.environments.terminal-pages.projects.jobs.terminal.650166e5.chunk.js.map


Source map error: Error: JSON.parse: unexpected character at line 1 
column 1 of the JSON data Resource URL: 
http://gitlab-buster.lxc/assets/webpack/pages.ide.da3ccd82.chunk.js 
Source Map URL: pages.ide.da3ccd82.chunk.js.map


Source map error: Error: JSON.parse: unexpected character at line 1 
column 1 of the JSON data Resource URL: 
http://gitlab-buster.lxc/assets/webpack/runtime.6c5d081d.bundle.js 
Source Map URL: runtime.6c5d081d.bundle.js.map


When switching to npmjs.com distributed xterm, the error is gone.

gitlab need xterm 3.14.5, so it is likely a version mismatch as well.

I will check with xterm 3.8.1 from npmjs.com to confirm if it is a 
version mismatch or not. If it is a version mismatch I'll retitle this 
as a request for new upstream version.


--
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#980062: nocheck build profile is broken - Error: Cannot find module 'babel-jest'

[Pirate Praveen]

Package: node-yaml,pkg-js-tools
Severity: important

When building node-yaml with nocheck build profile, the build fails

dh binary
  dh_update_autotools_config
  dh_autoreconf
  dh_auto_configure --buildsystem=nodejs
mkdir node_modules
internal/modules/cjs/loader.js:638
   throw err;
   ^

Error: Cannot find module 'babel-jest'
   at Function.Module._resolveFilename 
(internal/modules/cjs/loader.js:636:15)

   at Function.resolve (internal/modules/cjs/helpers.js:33:19)
   at [eval]:1:21
   at Script.runInThisContext (vm.js:122:20)
   at Object.runInThisContext (vm.js:329:38)
   at Object. ([eval]-wrapper:6:22)
   at Module._compile (internal/modules/cjs/loader.js:778:30)
   at evalScript (internal/bootstrap/node.js:590:27)
   at startup (internal/bootstrap/node.js:265:9)
   at bootstrapNodeJSCore (internal/bootstrap/node.js:623:3)
### babel-jest is required by debian/nodejs/./extlinks but not available
make: *** [debian/rules:8: binary] Error 1

DEB_BUILD_OPTIONS=nocheck DEB_BUILD_PROFILES=nocheck sbuild
should skip jest build dependency but extlinks fails to find the link 
when jest is not installed.


extlinks and extcopies should filter nocheck build profiles 
automatically or should support build profiles like,


babel-jest 

--
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#956423: Bullseye freeze is coming soon

[Pirate Praveen]

Control: severity -1 important

On Mon, 11 Jan 2021 18:39:31 +0100 Xavier  wrote:
> Hi all,
>
> Bullseye freeze is coming and we still have problems with 
node-request
> removal. In particular, node-jsdom is not easy to patch. I tried a 
patch

> (not approved by upstream) but it needs a lot of unavailable Node.js
> modules.
>
> Looking at the following list, it seems that only node-jsdom is
> important to update, others have no important reverse dependencies
> AFAIK, haven't they?
>
> List of problems (from dak):
> # Broken Depends:
> node-jsdom: node-jsdom
> node-jsonld: node-jsonld
> node-matrix-js-sdk: node-matrix-js-sdk
> node-millstone: node-millstone
> node-yarnpkg: yarnpkg

It is not easy to fix yarnpkg (See #980316), so lowering the severity 
to important. It means we will have to support node-request ourselves 
without upstream support. That is true for yarnpkg already, so 
supporting yarnpkg+node-request should be ok.


--
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#980291: Bug#980291: Bug#980291: Bug#980291: Bug#980294: libjs-jquery-flot: breaking API change

[Pirate Praveen]

On 2021, ജനുവരി 19 2:46:30 AM IST, Xavier  wrote:
>Le 18/01/2021 à 18:47, Pirate Praveen a écrit :
>Maintaining an unsupported version means taking the risk to be unable to
>backport a security fix during stable life and LTS (we already have many
>examples).
>_Before freeze_, I prefer having updated libraries, take the risk to
>break sometime something, and patch reverse dependencies (with an
>upstream PR when useful): breaking a little testing/unstable is not a

It is not about breaking as such, but breaking without coordination and 
planning that is the problem. We have a release team and transition process for 
a reason. I don't think uploading breaking changes without giving adequate 
notice and warning is OK.

>drama. But we are a team, if the team prefer to take the security risk,
>then OK, I'll stop updating any libjs-* package (and stop tearing my
>hair to patch obsolete packages when a CVE exists).

It is not black or white, either not update or update without coordination. 
There is grey in the middle update after giving sufficient time for people to 
respond.

>For the rhythm, most of libjs/node-* packages were strongly outdated in
>Buster, the sustained pace of 2020 only partially made up for the
>accumulated delay and the related technical debt.

These libraries are used by applications and having updated libraries but 
broken applications is not a good situation.

Finding which update broke your application when there are many updates is 
painful and stressful. If you at least know which update broke your application 
the situation is much better.

>Anyway, we entered freeze, it's not time to update anything not needed,
>except minor and tested updates, but I'm happy to have updated a lot of
>packages before freeze even if it has broken unstable sometime.
>I feel the [1] dashboard better now than before Buster release.
>
>[1]:
>https://udd.debian.org/dmd/?email1=pkg-javascript-devel%40lists.alioth.debian.org=html
>

I appreciate all your work in this regard, I'm only asking you to give more 
time between experimental to unstable updates and filing bugs in case some 
applications are in reverse dependencies and don't have functional tests.

I appreciate your work in getting tests enabled in more packages, but we don't 
have 100% test coverage so some tests have to be done manually and you need a 
warning for people to do that.
-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.

-- 
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#980406: This is confirmed as a bug in debian package

[Pirate Praveen]

Control: severity -1 serious

I was able to use xterm 3.8.1 from nmpjs.com with gitlab without any 
issues. So this is a bug in node-xterm debian build.


--
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#980291: Bug#980291: Bug#980294: libjs-jquery-flot: breaking API change

[Pirate Praveen]

On Mon, Jan 18, 2021 at 2:28 pm, Antonio Terceiro  
wrote:

But the fact is that all the other reverse dependencies that used any
plugin now need to be changed accordingly. Otherwise we can just wait
for their chart features to break in subtle ways in the face of users.


Not specific to this bug, but in general, we need to be a lot more 
careful and slow when updating node modules that also has libjs-* since 
we don't really have automated tests for them. For, node only parts we 
have tests most of the time, though not all packages have tests. So we 
have to be generally slow down on any major version update.


--
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#980314: leaflet-markercluster: switch to @rollup/plugin-json

[Pirate Praveen]

Package: leaflet-markercluster
Version: 1.4.1~dfsg-9
Severity: important

As tracked in
https://wiki.debian.org/Javascript/Nodejs/Transitions/Rollup-plugin-json-legacy-rm

and notified in 
https://alioth-lists.debian.net/pipermail/pkg-javascript-devel/2021-January/050132.html


It'd be good to drop the embedded copy of legacy rollup-plugin-json 
component from bullseye.


--
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#980313: leaflet: please switch to @rollup/plugin-json

[Pirate Praveen]

Package: leaflet
Version: 1.7.1~dfsg-2
Severity: important

As tracked in
https://wiki.debian.org/Javascript/Nodejs/Transitions/Rollup-plugin-json-legacy-rm

and notified in 
https://alioth-lists.debian.net/pipermail/pkg-javascript-devel/2021-January/050132.html


It'd be good to drop the embedded copy of legacy rollup-plugin-json 
component from bullseye.


--
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#980316: Update yarnpkg to 2.x versions using corepack repo

[Pirate Praveen]

Package: yarnpkg
Version: 1.22.10+~cs22.25.14-1
Severity: important
Control: block 956423 by -1

Yarn 1.x branch is not receiving any updates upstream. We somehow 
managed to get it build with newer versions of build dependencies for 
bullseye, but we are not able to remove dependency on request yet.


If we can package yarn 2.x branch using 
https://github.com/nodejs/corepack

we can move to an upstream supported branch.

I have tried to build this manually with taking some modules from 
npmjs.com


Filing this bug to keep track of this update.

New packages clipanion terser-webpack-plugin ts-loader 
@zkochan/cmd-shim (if you'd like to help, feel free to file ITP and add 
it as blocking this bug)


Probably embed @yarnpkg/fslib
terser need update to 4.8 and Jonas needs help

--
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#980316: starting with clipanion

[Pirate Praveen]

clipanion needs @wessberg/rollup-plugin-ts as build dependency

--
Pkg-javascript-devel mailing list
Pkg-javascript-devel@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel

Re: [Pkg-javascript-devel] Bug#980032: RM: node-request/2.88.1-5

[Pirate Praveen]

On Wed, Jan 13, 2021 at 12:22 pm, Xavier  wrote:

CC to pkg-javascript-devel for node-yarnpkg elements



We can try to update yarnpkg to version 2 by building corepack [1].

I need help with these packages,

New modules: clipanion terser-webpack-plugin  ts-loader 
@zkochan/cmd-shim


Update terser to 4.8 at least

I'm currently trying to update node-babel7 in buster-backports and it 
can take some more time before I can get to these.


We can embed a copy of request in yarnpkg as a last resort.

[1] https://github.com/nodejs/corepack



--
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#977689: node-postcss: please embed additional postcss extensions -import -url and more

[Pirate Praveen]

On Fri, 18 Dec 2020 23:17:16 +0100 Jonas Smedegaard  wrote:
> Package: node-postcss
> Version: 7.0.34-1
> Severity: wishlist
>
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA512
>
> I need these postcss-related modules not yet in Debian:
>
>  postcss-css-variables

I just looked at this and it needs postcss 6.x and I'm not sure if it 
is even compatible with postcss 8.x


I think embedding this in postcss will make transitions harder (we will 
have to update all plugins at once).


>  postcss-flexbugs-fixes
>  postcss-import
>  postcss-url
>  postcss-easings
>  postcss-extend
>  postcss-hexrgba
>  postcss-import
>  postcss-loader
>  postcss-mixins
>  postcss-nested
>  postcss-preset-env
>  postcss-scss
>  postcss-simple-vars
>  postcss-strip-inline-comments
>  sugarss
>  postcss-js
>  postcss-mixins
>
> they all seem light on dependencies and build-dependencies
> (modulo test-only build-dependencies).
> Please consider embedding them into the node-postcss package.
>
> (postcss-import depends on missing module read-cache - seems old, so 
not

> sure if that should be embedded too or maybe patched away somehow)
>
> (postcss-js depends on missing camelcase-css - see bug#977688)

I have not looked at other ones yet.

>  - Jonas

--
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#977688: node-css-loader: please embed additional postcss extensions

[Pirate Praveen]

On Fri, 18 Dec 2020 23:10:30 +0100 Jonas Smedegaard  wrote:
> I need these postcss-related modules not yet in Debian:
>
>  postcss-loader

Since it uses babel to build, I think it'd be better to package it 
separately.


>  postcss-preset-env

This is using rollup as a build system and has a large number of 
dependencies. I think this should be packaged separately too.


>  postcss-strip-inline-comments

This has a dependency on an old version of postcss (5.x) and runtime 
dependencies of many babel plugins so I'm not sure about it.


--
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#979208: libjs-source-map breaks ruby-terser with err ExecJS::ProgramError: ReferenceError: window is not defined

[Pirate Praveen]

package: libjs-source-map
version: 0.7.0++dfsg2+really.0.6.1-4
severity: grave
Control: affects -1 ruby-terser

Upstream npmjs.com dist tarball has the following at the top of 
dist/source-map.min.js


!function(e,n){"object"==typeof exports&&"object"==typeof 
module?module.exports=n():"function"==typeof 
define&?define([],n):"object"==typeof 
exports?exports.sourceMap=n():e.sourceMap=n()}(this,function(){return 
function(e){function n(t){if(r[t])return r[t].exports;


But debian package ships with the following ("window,function()" 
instead of "this,function()",


!function(e,n){"object"==typeof exports&&"object"==typeof 
module?module.exports=n():"function"==typeof 
define&?define([],n):"object"==typeof 
exports?exports.sourceMap=n():e.sourceMap=n()}(window,function(){return 
function(e){var n={};function r(t){if(n[t])return n[t].exports;


which breaks no browser environments like ruby execjs/rails assets 
pipeline.


This caused gitlab asset precompilation failure, which now switched to 
ruby-terser from earlier ruby-uglifier.


rake aborted!
ExecJS::ProgramError: ReferenceError: window is not defined
(execjs):441:200
(execjs):502:14
(execjs):1:40
Object. ((execjs):1:58)
Module._compile (internal/modules/cjs/loader.js:1015:30)
Object.Module._extensions..js (internal/modules/cjs/loader.js:1035:10)
Module.load (internal/modules/cjs/loader.js:879:32)
Function.Module._load (internal/modules/cjs/loader.js:724:14)
Function.executeUserEntryPoint [as runMain] 
(internal/modules/run_main.js:60:12)

internal/main/run_main_module.js:17:47
/usr/share/rubygems-integration/all/gems/terser-1.0.2/lib/terser.rb:183:in 
`context'
/usr/share/rubygems-integration/all/gems/terser-1.0.2/lib/terser.rb:223:in 
`run_terserjs'
/usr/share/rubygems-integration/all/gems/terser-1.0.2/lib/terser.rb:164:in 
`compile'
/usr/share/rubygems-integration/all/gems/terser-1.0.2/lib/terser/compressor.rb:45:in 
`call'
/usr/share/rubygems-integration/all/gems/terser-1.0.2/lib/terser/compressor.rb:23:in 
`call'
/usr/share/rubygems-integration/all/gems/actionview-6.0.3.4/lib/action_view/helpers/asset_url_helper.rb:201:in 
`asset_path'
/usr/share/gitlab/app/assets/javascripts/lib/ace/ace_config_paths.js.erb:22:in 
`block in _evaluate_template'
/usr/share/gitlab/app/assets/javascripts/lib/ace/ace_config_paths.js.erb:21:in 
`each'
/usr/share/gitlab/app/assets/javascripts/lib/ace/ace_config_paths.js.erb:21:in 
`_evaluate_template'
/usr/share/rubygems-integration/all/gems/rake-13.0.1/exe/rake:27:in 
`'

Tasks: TOP => assets:precompile
(See full trace by running task with --trace)

Upstream build is using webpack 1.12 where as we have webpack 4.43 so 
we need to update our webpack configuration.


As per 
https://dev.to/riversun/recipes-on-how-to-create-a-library-that-supports-both-browser-and-node-js-201m


we should add globalObject: 'this', to webpack configuration.

--
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#979042: node-rollup-plugin-commonjs: drop embedded copy of legacy plugin

[Pirate Praveen]

Control: fixed -1 17.0.0+repack-1

On Sat, 02 Jan 2021 16:39:48 +0530 Pirate Praveen 
 wrote:
> I plan to remove the embedded copy of legacy plugin (similar to how 
it
> was done for node-resolve and babel plugins) for bullseye. It is 
mostly
> a one line patch and we have to maintain only one copy of this 
module.


Uploaded to experimental.

--
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#979087: incompatible with node-postcss 8 and unmaintained

[Pirate Praveen]

Package: node-postcss-filter-plugins,node-postcss-minify-font-values
Severity: serious

Already filed request for removal. Filing rc bug in case the removal 
takes longer than auto removal from testing for node-postcss 8 testing 
migration.


--
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#979086: node-regexpp: empty vcs git repo

[Pirate Praveen]

Package: node-regexpp
Version: 3.1.0-4

Git repo of this package is empty. Please push the git repo to salsa.

--
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#979042: node-rollup-plugin-commonjs: drop embedded copy of legacy plugin

[Pirate Praveen]

Package: node-rollup-plugin-commonjs
Version: 15.1.0+~9.3.4-2
Severity: important
Owner: Pirate Praveen 

I plan to remove the embedded copy of legacy plugin (similar to how it 
was done for node-resolve and babel plugins) for bullseye. It is mostly 
a one line patch and we have to maintain only one copy of this module.


--
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#978933: node-rollup-plugin-babel: drop legacy plugin for bullseye

[Pirate Praveen]

Package: node-rollup-plugin-babel
Version: 5.2.1+repack+~4.4.0-2
Severity: important

I think we should try to remove the embedded copy of legacy plugin to 
reduce maintenance for bullseye (similar to how we did node-resolve 
plugin).


--
Pkg-javascript-devel mailing list
Pkg-javascript-devel@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel

Re: [Pkg-javascript-devel] node-redux_4.0.5-3_source.changes ACCEPTED into unstable

[Pirate Praveen]

On 2020, ഡിസംബർ 31 7:40:23 PM IST, Nicolas Mora  wrote:
>Hello,
>
>Thanks for the upload, although I remember I'm having problems with this 
>package salsa repo, I don't have admin access to it, therefore I can't 
>push to master branch. I made some changes I pushed in the branch 
>merge-master a few days ago [1].
>
>Can someone from the team grant me admin for this repo? then I'll 
>reapply or cleanup my changes.

You have maintainer access now.
-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.

-- 
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#979087: incompatible with node-postcss 8 and unmaintained

[Pirate Praveen]

Control: reassign -1 node-postcss-minify-font-values

On Sat, 02 Jan 2021 21:48:11 +0530 Pirate Praveen 
 wrote:

> Package: node-postcss-filter-plugins,node-postcss-minify-font-values
> Severity: serious
>
> Already filed request for removal. Filing rc bug in case the removal
> takes longer than auto removal from testing for node-postcss 8 
testing

> migration.

node-postcss-filter-plugins already has an rc bug.

--
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#977535: pkg-js-tools should create node_modules symlink in autopkgtest

[Pirate Praveen]

Package: pkg-js-tools,node-d3-geo
Severity: important

node-d3-geo autopkgtest is failing with

Error: Cannot find module '@babel/register'

https://ci.debian.net/data/autopkgtest/testing/amd64/n/node-d3-geo/8873707/log.gz

Even though debian/nodejs/extlinks has @babel/register.

I don't know if we should handle it specifically for this package or do it for 
all
-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.-- 
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#977535: Bug#977535: pkg-js-tools should create node_modules symlink in autopkgtest

[Pirate Praveen]

Control: clone -1 -2
Control: reassign -2 pkg-js-tools
Control: retitle -2 use cp -rL for extcopies (needed for symlinks)
Control: reassign node-d3-geo,pkg-js-tools,node-tape

On Wed, Dec 16, 2020 at 8:27 am, Xavier  wrote:

Hi,

when using tsc, if /usr/share/nodejs/foo is linked in
debian/nodejs/extlinks and requires another file linked in
debian/nodejs/extlinks, this fails because tsc search a "node_modules"
directory starting from /usr/share/nodejs/foo (see typescript bug
https://github.com/microsoft/TypeScript/issues/33661).

To avoid this, use debian/nodejs/extcopies.


No, that did not fix the autopkgtest. tape needs @babel/register in 
node_modules. The problem is not symlinks vs copies, but during 
autopkgtest, @babel/register is not found by tape. Symbolic links 
(extlinks) is enough in this case as tests work during build with 
symbolic links.


So extlinks or extcopies should be respected for autopkgtests also I 
think. Or we need to fix node-tape to look in global paths. We can 
reassign to correct package once we decide where it should be fixed.


And for extcopies, I am cloning this as another bug. cp -r will create 
broken symbolic links as many of our node packages include symbolic 
links, for example node-font-awesome (provided by fonts-font-awesome) 
or node-terser. So we should use cp -rL to dereference symbolic links.


--
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#977535: Bug#977535: Bug#977535: pkg-js-tools should create node_modules symlink in autopkgtest

[Pirate Praveen]

Control: reassign -1 node-d3-geo,pkg-js-tools,node-tape,node-resolve

On Wed, Dec 16, 2020 at 4:26 pm, Pirate Praveen 
 wrote:
So extlinks or extcopies should be respected for autopkgtests also I 
think. Or we need to fix node-tape to look in global paths. We can 
reassign to correct package once we decide where it should be fixed.


tape is using node-resolve here, so another possibility is to fix 
node-resolve to add debian's global paths for resolution.


--
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#958687: node-request-promise: Remove dependency to node-request

[Pirate Praveen]

On Fri, 24 Apr 2020 13:52:39 +0200 y...@debian.org wrote:
> Package: node-request-promise
> Severity: important
> Control: block 956423 by -1
>
> Upstream has deprecated node-request:
> https://github.com/request/request/issues/3142
>
> It can be replaced by node-got
>
>

node-request-promise has no reverse (build) dependencies, so I think we 
can request removal.


pravi@ilvala2:~$ reverse-depends node-request-promise
No reverse dependencies found
pravi@ilvala2:~$ reverse-depends -b node-request-promise
No reverse dependencies found
pravi@ilvala2:~$

--
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#958689: node-request-promise-core: Remove dependency to node-request

[Pirate Praveen]

Control: block -1 by 958697

On Fri, 24 Apr 2020 13:52:39 +0200 y...@debian.org wrote:
> Package: node-request-promise-core

Only reverse (build) dependency is node-jsdom (and node-request-promise 
- which can be removed) so if node-jsdom is fixed, we can remove this 
package.


--
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#977535: Bug#977535: Bug#977535: pkg-js-tools should create node_modules symlink in autopkgtest

[Pirate Praveen]

On Wed, Dec 16, 2020 at 12:15 pm, Xavier  wrote:

Could you try pkg-js-autopkgtest 0.9.55 (experimental + salsa) ?


No, this did not work. I don't see any cp command in the logs.

autopkgtest [17:03:46]: test pkg-js-autopkgtest: 
/usr/share/pkg-js-autopkgtest/runner
autopkgtest [17:03:46]: test pkg-js-autopkgtest: 
[---

# Using package.json
# Node module name is d3-geo
# Build files found: .babelrc rollup.config.js
# Test files found: test
# Files/dir to be installed from source: test .babelrc rollup.config.js
# Copy test files
# Copy debian/tests/pkg-js content
'debian/tests/pkg-js' -> 
'/tmp/autopkgtest.6RglHt/autopkgtest_tmp/smokelTQtji/debian/tests/pkg-js'
'debian/tests/pkg-js/test' -> 
'/tmp/autopkgtest.6RglHt/autopkgtest_tmp/smokelTQtji/debian/tests/pkg-js/test'

# Found debian/tests/test_modules directory, let's copy it
'/tmp/autopkgtest.6RglHt/autopkgtest_tmp/smokelTQtji/node_modules/topojson-client' 
-> '../debian/tests/test_modules/topojson-client'
'/tmp/autopkgtest.6RglHt/autopkgtest_tmp/smokelTQtji/node_modules/world-atlas' 
-> '../debian/tests/test_modules/world-atlas'

# Searching module in /usr/lib/nodejs/d3-geo
# Searching module in /usr/lib/*/nodejs/d3-geo
# Searching module in /usr/share/nodejs/d3-geo
# Found /usr/share/nodejs/d3-geo
# Searching files to link in /usr/share/nodejs/d3-geo
'./dist' -> '/usr/share/nodejs/d3-geo/dist'
'./package.json' -> '/usr/share/nodejs/d3-geo/package.json'
'./src' -> '/usr/share/nodejs/d3-geo/src'
# Launch debian/tests/pkg-js/test with sh -ex
+ tape -r @babel/register test/**/*.js
/usr/share/nodejs/resolve/lib/sync.js:92
   throw err;
   ^

Error: Cannot find module '@babel/register' from 
'/tmp/autopkgtest.6RglHt/autopkgtest_tmp/smokelTQtji'


Also in the debci logs I don't see a symlink created either (with 
extlinks). So the bug seems not reading both extlinks and extcopies.


https://ci.debian.net/data/autopkgtest/testing/amd64/n/node-d3-geo/8873707/log.gz

--
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#977535: Bug#977535: Bug#977535: Bug#977535: pkg-js-tools should create node_modules symlink in autopkgtest

[Pirate Praveen]

On Wed, Dec 16, 2020 at 1:07 pm, Xavier  wrote:

I didn't add an "echo" but debian/nodejs/extcopies are really copied
(verified). Add a `ls node_modules` in your debian/tests/pkg-js/test 
if

you want to verify


# Launch debian/tests/pkg-js/test with sh -ex
+ ls node_modules
topojson-client
world-atlas
+ cat debian/nodejs/extcopies
cat: debian/nodejs/extcopies: No such file or directory
autopkgtest [17:41:46]: test pkg-js-autopkgtest: 
---]
autopkgtest [17:41:46]: test pkg-js-autopkgtest:  - - - - - - - - - - 
results - - - - - - - - - -

pkg-js-autopkgtest   FAIL non-zero exit status 1
autopkgtest [17:41:46]:  summary
pkg-js-autopkgtest-require PASS (superficial)
pkg-js-autopkgtest   FAIL non-zero exit status 1
pravi@mahishi:~/forge/js-team/node-d3-geo$ apt policy pkg-js-tools
pkg-js-tools:
 Installed: 0.9.55
 Candidate: 0.9.55
 Version table:
*** 0.9.55 100
   100 /var/lib/dpkg/status
0.9.54 500
   500 http://deb.debian.org/debian sid/main amd64 Packages

Can you try running autopkgtest for node-d3-geo?

--
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#986117: take ownership and mark as pending

[Pirate Praveen]

On Tue, 1 Jun 2021 16:41:51 +0200 Paolo Greppi  
wrote:

> owner 986117 Paolo Greppi 
> tag 986117 pending

Hi Paolo,

Can you upload it?

Thanks
Praveen

--
Pkg-javascript-devel mailing list
Pkg-javascript-devel@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel

Re: [Pkg-javascript-devel] [RFS] node-tar

[Pirate Praveen]

On Sat, Jun 12, 2021 at 2:54 pm, Ayoyimika Ajibade 
 wrote:

Hi there,

I have updated the node-tar  from version 6.0.5+ds1+~cs11.3.9-1 to 
6.1.0+ds1+~cs11.3.9-1 The package is available at 
https://salsa.debian.org/Ayoyimika/node-tar/ and I am requesting for 
sponsorship and I ensured all tests passes, it's lintian clean and 
also built it in a clean chroot with sbuild.Thanks



Uploaded, thanks! Btw you don't need to add 'Uploaded to experimental' 
in changelog next time. Also you can request membership in js-team 
group in salsa.

Ayoyimika Ajibade





--
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#990052: Looks like this transition is not completed

[Pirate Praveen]

Control: forwarded -1 
https://github.com/DefinitelyTyped/DefinitelyTyped/pull/44365

Seems this transition is not completed.



pEpkey.asc
Description: application/pgp-keys
-- 
Pkg-javascript-devel mailing list
Pkg-javascript-devel@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel

Re: [Pkg-javascript-devel] [RFS] -- node-memfs

[Pirate Praveen]

I think we don't have to wait, we can upload -2 with the changes.

On 2021, ജൂൺ 23 5:09:12 PM IST, Yadd  wrote:
>Le 23/06/2021 à 13:34, Tunji a écrit :
>> Hi, in the first packaging of memfs I did, I realized that the
>embedded
>> package (fs-monkey) was not installable, so in this update I made I
>> fixed that problem by listing fs-monkey as a component to install in
>> nodejs root directory, I update changelog with commits and version
>> number.
>> Kindly inspect if package is fit for sponsorship.
>
>Hi,
>
>first, pkg-javascript-devel@alioth-lists.debian.net and
>pkg-javascript-de...@alioth-lists.debian.org are the same list, please
>stop double send.
>
>For node-memfs, we will wait for ftpmaster acceptance, then update what
>is needed (I already fixed autopkgtest). You can push your work to
>js-team/node-memfs
>
>Cheers,
>Yadd
>
>--
>Pkg-javascript-devel mailing list
>Pkg-javascript-devel@alioth-lists.debian.net
>https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel

-- 
Sent from my p≡p for Android.
-- 
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#990052: Drop @types/jest, replaced by @jest/types

[Pirate Praveen]

Package: jest
Version: 26.6.3+repack+~cs64.44.39-3
Severity: important

@types/jest is now obsolete as jest itself provides type definitions in 
@jest/types module (already shipped in the package). When using 
@types/jest, it results in error finding dependencies, for example in 
node-memfs with fs-monkey as component.


--
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#989733: webpack: Error: Cannot find module 'array-back'

[Pirate Praveen]

Package: webpack
Version: 5.6.0+~cs6.4.0-1~exp2
Severity: serious

With webpack from experimental,

webpack --help
(node:251750) UnhandledPromiseRejectionWarning: Error: Cannot find 
module 'array-back'

Require stack:
- /usr/share/nodejs/webpack/node_modules/command-line-usage/index.js
- /usr/share/nodejs/webpack-cli/lib/groups/runHelp.js
- /usr/share/nodejs/webpack-cli/lib/utils/arg-parser.js
- /usr/share/nodejs/webpack-cli/lib/webpack-cli.js
- /usr/share/nodejs/webpack-cli/lib/bootstrap.js
- /usr/share/nodejs/webpack-cli/bin/cli.js
- /usr/share/nodejs/webpack/bin/webpack.js
   at Function.Module._resolveFilename 
(internal/modules/cjs/loader.js:815:15)

   at Function.Module._load (internal/modules/cjs/loader.js:667:27)
   at Module.require (internal/modules/cjs/loader.js:887:19)
   at require 
(/usr/share/nodejs/webpack/node_modules/v8-compile-cache/v8-compile-cache.js:159:20)
   at commandLineUsage 
(/usr/share/nodejs/webpack/node_modules/command-line-usage/index.js:12:20)
   at printHelp 
(/usr/share/nodejs/webpack-cli/lib/groups/runHelp.js:71:12)
   at outputHelp 
(/usr/share/nodejs/webpack-cli/lib/groups/runHelp.js:111:20)
   at argParser 
(/usr/share/nodejs/webpack-cli/lib/utils/arg-parser.js:45:9)

   at runCLI (/usr/share/nodejs/webpack-cli/lib/bootstrap.js:11:24)
   at Object. 
(/usr/share/nodejs/webpack-cli/bin/cli.js:24:5)
(node:251750) UnhandledPromiseRejectionWarning: Unhandled promise 
rejection. This error originated either by throwing inside of an async 
function without a catch block, or by rejecting a promise which was not 
handled with .catch(). To terminate the node process on unhandled 
promise rejection, use the CLI flag `--unhandled-rejections=strict` 
(see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). 
(rejection id: 1)
(node:251750) [DEP0018] DeprecationWarning: Unhandled promise 
rejections are deprecated. In the future, promise rejections that are 
not handled will terminate the Node.js process with a non-zero exit 
code.


--
Pkg-javascript-devel mailing list
Pkg-javascript-devel@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel

Re: [Pkg-javascript-devel] RFS: node-lru-cache

[Pirate Praveen]

On Fri, Jun 11, 2021 at 4:49 pm, Harish  
wrote:

Hi,

I've just update node-lru-cache package to a  new upstream version 
(5.1.1 ->6.0.0) , the package is available at 
:https://salsa.debian.org/Harish1/node-lru-cache   I ensured all 
tests passes, it's Lintian clean and also built it in a clean Chroot 
with Sbuild.


Please consider to review and upload it .



This is a major version update, did you test if all reverse 
dependencies still work?


$ reverse-depends node-lru-cache
Reverse-Depends
* node-cacache
* node-hosted-git-info
* node-js-beautify
* node-jsonld
* node-semver

$ reverse-depends -b node-lru-cache
Reverse-Build-Depends
* node-cacache
* node-ejs
* node-hosted-git-info
* node-js-beautify
* node-jsonld
* node-semver


Regards,

harish.




--
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#988507: update node-terser to alteast version 4.8

[Pirate Praveen]

Package: node-terser
Version: 4.1.2-8
Severity: wishlist
Control: block 988506 by -1

terser-webpack-plugin needs terser at least version 4.8. Is there any 
known blockers I can help with?


--
Pkg-javascript-devel mailing list
Pkg-javascript-devel@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel

Re: [Pkg-javascript-devel] [RFS] node-caniuse-lite

[Pirate Praveen]

> Hi there 
> I've just updated the node-caniuse-lite package to a new upstream 
version and I wish to find a sponsor to help me

> upload this changes to the Debian node-caniuse-lite repository.
> I ensured it's lintian clean and also built it in a clean chroot 
with sbuild.
> Find the changes at: 
https://salsa.debian.org/sonnie/node-caniuse-lite

> RegardsSunday Nkwuda

I have uploaded it, thanks for your work!



--
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#988559: Bug#988559: Support reading from lerna.json to find components automatically

[Pirate Praveen]

On Sat, May 15, 2021 at 8:30 pm, Yadd  wrote:

Le 15/05/2021 à 20:18, Pirate Praveen a écrit :

 Package: pkg-js-tools
 Version: 0.9.65
 Severity: wishlist

 Example module @toast-ui/editor

 Read lerna.json and install these similar to entries in
 debian/nodejs/components

 {
 "packages": ["apps/*", "plugins/*", "libs/*"],
 "version": "2.1.0"
 }


Hi,

pkg-js-tools doesn't modify debian/* files for now. Maybe this is the
job of npm2deb ?


That will work too, or pkg-js-tools could read this directly, may be 
npm2deb is better option.


--
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#988559: Support reading from lerna.json to find components automatically

[Pirate Praveen]

Package: pkg-js-tools
Version: 0.9.65
Severity: wishlist

Example module @toast-ui/editor

Read lerna.json and install these similar to entries in 
debian/nodejs/components


{
 "packages": ["apps/*", "plugins/*", "libs/*"],
 "version": "2.1.0"
}

--
Pkg-javascript-devel mailing list
Pkg-javascript-devel@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel

Re: [Pkg-javascript-devel] [RFS] node-typanion

[Pirate Praveen]

On Sat, May 15, 2021 at 5:33 pm, Yadd  wrote:

Le 08/05/2021 à 02:08, Sonnie Nkwuda a écrit :

 Hi there 

 I've just packaged a new node module, node-typanion 3.3.1, for 
Debian

 and I wish to find a sponsor to help me upload it to salsa Debian
 js-team repository.
 I ensured it's lintian clean and also built it in a clean chroot 
with

 sbuild.

 Find it at:  https://salsa.debian.org/sonnie/node-typanion
  .

 Regards
 Sunday Nkwuda


Hi,

looks good, thanks. Build & autopkgtest & duck & lintian are OK. Just
some few things:

 * copyright is 2020, not 2021
 * in debian/tests/pkg-js/test:

 TS_NODE_TRANSPILE_ONLY=true

   has no effect, it should be removed or fixed:

 export TS_NODE_TRANSPILE_ONLY=true

 * in debian/control:
   * test-only build-dependencies should be marked with 
 (probably mocha and chai)
   * remove pkg-js-tools dependency: double with dh-sequence-nodejs

Sorry to not have look at this earlier, I'm hospitalized.


$ rmadison node-typanion
node-typanion | 3.3.1-1   | new| source, all

I had uploaded it already, these changes can be made as version 3.3.1-2.



--
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#988602: Include babel-plugin-module-resolver with node-babel7

[Pirate Praveen]

Package: node-babel7
Version: 7.12.12+~cs150.141.84-6
Severity: wishlist

babel-plugin-module-resolver is a build dependency of cssnano

--
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#987967: jade replaced by pug for ages, doesn't work anymore

[Pirate Praveen]

On Sun, 2 May 2021 23:24:36 +0200 =?UTF-8?Q?Stefan_B=c3=bchler?= 
 wrote:

> Package: node-jade
> Version: 1.11.0+~cs4.1.0-1
> Severity: grave
>
> Hi,
>
> https://www.npmjs.com/package/jade says last release was 6 years ago 
and

> it got replaced by pug.
>
> Also it doesn't work anymore in bullseye for two reasons:

I think we can request removal of node-jade from bullseye and if/when 
pug is packaged, remove it from unstable as well. Since isso is not in 
bullseye this should not affect any other package.


--
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#988884: libsass and node-node-sass is deprecated upstream

[Pirate Praveen]

Package: libsass, node-node-sass
Severity: important

libsass and node-sass seems deprecated by upstream in favor of dart 
sass.


https://sass-lang.com/blog/libsass-is-deprecated

I was trying to package rollup-plugin-sass and noticed it is using sass 
module and not node-sass module.


I tried a simple patch to replace sass with node-sass in 
rollup-plugin-sass, but build was failing when trying to bundle it.


I will try packaging dart-sass, but I have never touched a package 
written in dart yet.


--
Pkg-javascript-devel mailing list
Pkg-javascript-devel@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel

Re: [Pkg-javascript-devel] [RFS] node-clipanion

[Pirate Praveen]

> Hi there 
> I've just packaged a new node module, node-clipanion 2.6.2, for 
Debian
> and I wish to find a sponsor to help upload it to salsa Debian 
js-team

> repository.

> I ensured all tests passes, it's lintian clean and also built it in a
> clean chroot with sbuild.Find it 
at:https://salsa.debian.org/sonnie/node-

> clipanion

> Please note: node-clipanion requires @types/chai-as-promised which is
> provided by the new update of node-chai-as-promised at:
> https://salsa.debian.org/sonnie/node-chai-as-promised

> Kindly upload this node-chai-as-promised update also, along with the 
new

> node-clipanion package
>Regards
> Sunday

Hi Sonnie,

I uploaded both packages. Thanks for your contribution!

Cheers
Praveen



--
Pkg-javascript-devel mailing list
Pkg-javascript-devel@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel

Re: [Pkg-javascript-devel] Processed: BTS housekeeping and severity adjustments

[Pirate Praveen]

On 2021, ജൂൺ 1 1:23:22 PM IST, Paolo Greppi  wrote:
>Il 31/05/21 23:33, Debian Bug Tracking System ha scritto:
>> Processing commands for cont...@bugs.debian.org:
>> 
>>> severity 986117 serious
>> Bug #986117 [yarnpkg] yarnpkg is not compatible with node-proper-lockfile 
>> 3.0.0+
>> Severity set to 'serious' from 'normal'
>> ...
>
>Hu everybody, I have drafted a patch for this issue:
>https://salsa.debian.org/js-team/node-yarnpkg/-/blob/master/debian/patches/19-proper-lockfile.diff
>
>Any comments?

If the command that failed now works, that would be a good indicator, right?

>Paolo
>

-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.

-- 
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#990458: babel umd support is limited

[Pirate Praveen]

On Sat, 03 Jul 2021 23:01:35 +0530 Pirate Praveen 
 wrote:
> I switched to rollup for generating umd and removed 
add-module-exports
> plugin and it is working now. Possibly defining "autosize" global 
with

> @babel/plugin-transform-modules-umd without add-module-exports plugin
> would have worked as well.

I tried this option today and it did not work. Looks like this is a 
known limitaion of babel umd plugin. 
https://github.com/babel/babel/issues/10696 so we will stick with 
rollup.


--
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#990458: libjs-autosize is not fixed by node-babel-plugin-add-module exports update

[Pirate Praveen]

Control: reopen -1

On Wed, 30 Jun 2021 22:40:13 +0530 Pirate Praveen 
 wrote:

> and this is working with diaspora. Thanks again for tracking down the
> issue.

Looks like I was wrong here and it is still failing with libjs-autosize 
built with latest node-babel-plugin-add-module-exports.


You can see this on browser console of 
https://diaspora.publicvm.com/statistics (setup by Rojin for testing).


--
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#990458: libjs-autosize is not fixed by node-babel-plugin-add-module exports update

[Pirate Praveen]

On Sat, Jul 3, 2021 at 12:29 pm, Akshay S Dinesh  
wrote:

https://stackoverflow.com/questions/33505992/babel-6-changes-how-it-exports-default

But most importantly 
https://kentcdodds.com/blog/misunderstanding-es6-modules-upgrading-babel-tears-and-a-solution


But this is babel 6 to babel 7 migration. The code transpiled by babel 
6 works fine, but moving to babel 7 broke it.


and looks like autosize upstream moved their build system to 
microbundle (an absctraction of rollup and babel with a set of plugins) 
which is not packaged yet.


--
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#990458: libjs-autosize is not fixed by node-babel-plugin-add-module exports update

[Pirate Praveen]

On Sat, 03 Jul 2021 18:11:20 +0530 Pirate Praveen 
 wrote:
> But this is babel 6 to babel 7 migration. The code transpiled by 
babel

> 6 works fine, but moving to babel 7 broke it.

One possibility is that the add-module-exports plugin is not compatible 
with babel 7's umd plugin (@babel/plugin-transform-modules-umd).


--
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#990458: autosize build is broken (throws error is diaspora web console)

[Pirate Praveen]

Package: libjs-autosize
Severity: grave
Version: 4.0.2~dfsg1-5
Control: affects -1 ruby-rails-assets-autosize,diaspora

I think during transition to babel7 something broke.

This causes diaspora ui to break,

Uncaught ReferenceError: module is not defined
   at 
main-e074888ae8b7a9cd9ffd9335b56c44872cea8212be3599667e8dd56947c37546.js:3
   at $.fn.charCount 
(main-e074888ae8b7a9cd9ffd9335b56c44872cea8212be3599667e8dd56947c37546.js:3)
   at 
main-e074888ae8b7a9cd9ffd9335b56c44872cea8212be3599667e8dd56947c37546.js:3


This leads to,

(t((t={exports:{}}).exports),e.autosize=t.exports)}("undefined"!=typeof 
globalThis?globalThis:"undefined"!=typeof 
self?self:this,function(e){"use strict";function n(a){function e(){var 
e=window.getComputedStyle(a,null);"vertical"===e.resize?a.style.resize="none":"both"===e.resize&&(a.style.resize="horizontal"),r="content-box"===e.boxSizing?-(parseFloat(e.paddingTop)+parseFloat(e.paddingBottom)):parseFloat(e.borderTopWidth)+parseFloat(e.borderBottomWidth),isNaN(r)&&(r=0),i()}function 
o(e){var 
t=a.style.width;a.style.width="0px",a.offsetWidth,a.style.width=t,a.style.overflowY=e}function 
n(e){for(var t=[];e&& instanceof 
Element;)e.parentNode.scrollTop&({node:e.parentNode,scrollTop:e.parentNode.scrollTop}),e=e.parentNode;return 
t}function s(){var 
e,t;0!==a.scrollHeight&&(e=n(a),t=document.documentElement&,a.style.height="",a.style.height=a.scrollHeight+r+"px",l=a.clientWidth,e.forEach(function(e){e.node.scrollTop=e.scrollTop}),t&&(document.documentElement.scrollTop=t))}function 
i(){s();var 
e=Math.round(parseFloat(a.style.height)),t=window.getComputedStyle(a,null),n="content-box"===t.boxSizing?Math.round(parseFloat(t.height)):a.offsetHeight;if(nr,l,c,u,d;a&&&"TEXTAREA"===a.nodeName&&!p.has(a)&&(c=l=r=null,u=function 
u(){a.clientWidth!==l&()},d=function(t){window.removeEventListener("resize",u,!1),a.removeEventListener("input",i,!1),a.removeEventListener("keyup",i,!1),a.removeEventListener("autosize:destroy",d,!1),a.removeEventListener("autosize:update",i,!1),Object.keys(t).forEach(function(e){a.style[e]=t[e]}),p["delete"](a)}.bind(a,{height:a.style.height,resize:a.style.resize,overflowY:a.style.overflowY,overflowX:a.style.overflowX,wordWrap:a.style.wordWrap}),a.addEventListener("autosize:destroy",d,!1),"onpropertychange"in 
a&&"oninput"in 
a&("keyup",i,!1),window.addEventListener("resize",u,!1),a.addEventListener("input",i,!1),a.addEventListener("autosize:update",i,!1),a.style.overflowX="hidden",a.style.wordWrap="break-word",p.set(a,{destroy:d,update:i}),e())}function 
t(e){e=p.get(e);e&()}function 
i(e){e=p.get(e);e&()}e["default"]=void 0;var 
a,o,p="function"==typeof Map?new Map:(a=[],o=[],{has:function 
r(e){return-1o[a.indexOf(e)]},set:function 
c(e,t){-1===a.indexOf(e)&&(a.push(e),o.push(t))},"delete":function 
u(e){e=a.indexOf(e);-1m(e){return new Event(e,{bubbles:!0})};try{new 
Event("test")}catch(d){m=function m(e){var 
t=document.createEvent("Event");return t.initEvent(e,!0,!1),t}}var 
s=null;"undefined"==typeof window||"function"!=typeof 
window.getComputedStyle?((s=function s(e){return 
e}).destroy=function(e){return e},s.update=function(e){return 
e}):((s=function s(e,t){return 
e&(e.length?e:[e],function(e){return 
n(e,t)}),e}).destroy=function(e){return 
e&(e.length?e:[e],t),e},s.update=function(e){return 
e&(e.length?e:[e],i),e}),e["default"]=s,module.exports=exports["default"]}),$.fn.charCount=function(i)


--
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#990458: Attaching the files from buster vs bullseye

[Pirate Praveen]

On Tue, 29 Jun 2021 23:54:30 +0530 Pirate Praveen 
 wrote:

> I can confirm libjs-autosize from buster works fine with diaspora.

So workaround is to install the buster version from snapshot.debian.org

http://snapshot.debian.org/archive/debian/20190209T090056Z/pool/main/a/autosize.js/libjs-autosize_4.0.2~dfsg1-3_all.deb

--
Pkg-javascript-devel mailing list
Pkg-javascript-devel@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel