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
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
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
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
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
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
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
>
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
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:
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]
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
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 i
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
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
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
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
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
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,
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
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.
--
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
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: └ Complete
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 vers
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
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
&g
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
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
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/Jav
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
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
post
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
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
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
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
--
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
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
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
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
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
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
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 @babe
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
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
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
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
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
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
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
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
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
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;
^
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
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_,
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
> ta
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
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
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
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
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.
--
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]:
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
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
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
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
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
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
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
-
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
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
> 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
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
{
"pac
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
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
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
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
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
> 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
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
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
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.
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
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/
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
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/li
801 - 900 of 992 matches
Mail list logo
