Package: node-escope
Severity: important
Control: affects -1 node-eslint-plugin-eslint-plugin
node-escope upstream project is unmaintained and its only reverse
dependency node-eslint-plugin-eslint-plugin has updated its dependency
to a maintained fork of escope, ie, eslint-scope in its new
> Hi there
> I've just made a few minor updates to node-d3-time and I wish to
find a
> sponsor to help me upload this changes to the debian node-d3-time
> repository.I ensured it's lintian clean ( except for gpg signature
warn
> which I guess the sponsor will sign).I also built it in a
Hi
I have recorded a video demo of updating a node package to new upstream
version. Hope it is useful to new people joining the team.
https://peertube.debian.social/videos/embed/fa67f177-2024-4ce8-9318-4d0e3d40cc14
Thanks
Praveen
--
Sent from my Android device with K-9 Mail. Please excuse my
On 2021, ഏപ്രിൽ 21 1:19:16 PM IST, Andreas Tille wrote:
>Hi folks,
>
>sorry for the long receiver list of this mail. As it was discussed[1]
>on debian-ai list about tensorflow dependencies, the package
>node-aws-sdk seems to be needed. Since there was some work on this
>package in Git[2] I
On Fri, 08 Jan 2021 16:04:05 +0530 Pirate Praveen
wrote:
> 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.
Thanks to
https://salsa.debian.org/js-t
On 2021, മാർച്ച് 18 8:22:54 PM IST, Andrius Merkys wrote:
>Hello,
>
>On 2021-03-15 13:45, Pirate Praveen wrote:
>> On 2021, മാർച്ച് 15 4:21:37 PM IST, Nilesh Patra wrote:
>>>> $ node-sass
>>>> /usr/share/nodejs/normalize-package-data/lib/fixer.
On 2021, മാർച്ച് 15 11:55:19 AM IST, Andrius Merkys wrote:
>Hello,
>
>On 2021-03-14 14:49, VIVEK K J wrote:
>> I've been modified node-agent-base package for including
>> typescript definitions.. The modified repo is available at
>> https://salsa.debian.org/vivekkj/node-agent-base .
>>
On 2021, മാർച്ച് 15 4:21:37 PM IST, Nilesh Patra wrote:
>> Dear Maintainer,
>>
>> * What led up to the situation?
>>
>> I installed node-node-sass, and ran its installed binary node-sass.
>>
>> * What exactly did you do (or not do) that was effective (or
>> ineffective)?
>>
>> Ran the
On 2021, മാർച്ച് 15 2:13:10 PM IST, Andrius Merkys wrote:
>On 2021-03-15 09:24, Pirate Praveen wrote:
>> On 2021, മാർച്ച് 15 11:55:19 AM IST, Andrius Merkys
>> wrote:
>>> On 2021-03-14 14:49, VIVEK K J wrote:
>>>>I've been modified node-agent-base p
On 2021, മാർച്ച് 15 11:55:19 AM IST, Andrius Merkys wrote:
>Hello,
>
>On 2021-03-14 14:49, VIVEK K J wrote:
>> I've been modified node-agent-base package for including
>> typescript definitions.. The modified repo is available at
>> https://salsa.debian.org/vivekkj/node-agent-base .
>>
[Ccing debian-release]
On Wed, 17 Feb 2021 14:01:40 + Julian Gilbey wrote:
> On Sun, Feb 14, 2021 at 02:26:30PM +0100, Jonas Smedegaard wrote:
> > I still recommend to request release team to ignore for this release
> > instead of lowering sverity, but don't care anough about this
On Sun, 13 Dec 2020 21:30:41 +0100 Jonas Smedegaard wrote:
> Package: node-uglifyjs-webpack-plugin
> Version: 1.3.0-9
> Severity: serious
>
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA512
>
> node-uglifyjs-webpack-plugin is dead since 1.5 years, already carries a
> patch to not actually use
On 2021, ഫെബ്രുവരി 14 2:55:33 PM IST, Jonas Smedegaard wrote:
>Quoting Pirate Praveen (2021-02-14 08:32:08)
>>
>>
>> On 2021, ഫെബ്രുവരി 14 12:44:09 PM IST, Julian Gilbey wrote:
>> >webpack depends on node-uglifyjs-webpack-plugin, which in turn has a
>> &g
On 2021, ഫെബ്രുവരി 14 12:44:09 PM IST, Julian Gilbey wrote:
>Source: node-webpack
>Version: 4.43.0-6
>Severity: serious
>
>webpack depends on node-uglifyjs-webpack-plugin, which in turn has a
>serious bug report against it because it is abandoned upstream.
We should reduce severity of that bug
On 2021, ഫെബ്രുവരി 5 6:36:09 PM IST, Nilesh Patra wrote:
>On Fri, 5 Feb, 2021, 4:49 pm Xavier, wrote:
>
>>
>> A big thank you to all of you for this good job!
>>
>
>Many thanks to you as well, for keeping a huge pile of packages in great
>shape! :-)
+1 thanks for creating pkg-js-tools and
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
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
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 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_,
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
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
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 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
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
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
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
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 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
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;
^
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, 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 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
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
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
Package: node-lodash
Version: 4.17.20+dfsg+~cs8.31.172-1
Severity: important
Control: affects -1 gitlab
Control: tags -1 help
gitlab package from salsa master-13.5 branch fails with this error
during installation.
ERROR in
/environments/components/environments_table.vue?vue=script=js&
On Wed, Jan 6, 2021 at 7:54 pm, Pirate Praveen
wrote:
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.
Good news. I got a working yarn 2 build
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 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 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 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
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
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: 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
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-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
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
--
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
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
Hi,
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
On Tue, Dec 29, 2020 at 20:02, Ben Finney wrote:
Control: found -1 webpack/4.43.0-6
On 16-Jun-2020, Ben Finney wrote:
On 18-May-2020, Pirate Praveen wrote:
>
https://salsa.debian.org/js-team/node-clone/-/blob/master/clone.js#L109
> I think we may need to embed older version of
Package: node-rollup-plugin-node-resolve
Version: 10.0.0+repack+~4.2.4-1
severity: important
At least autoprefixer-rails build is broken with version 10.
https://github.com/ai/autoprefixer-rails/pull/200#issuecomment-751924645
Probably more builds are silently broken.
While at it, I think we
On Fri, 25 Dec 2020 20:58:20 +0530 Pirate Praveen
wrote:
> 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]
Control: reassign -1 node-css-loader
Control: retitle -1 autopkgtest regression due to stderr
On Sat, Dec 26, 2020 at 10:50, Xavier wrote:
Le 26/12/2020 à 10:45, Pirate Praveen a écrit :
Package: pkg-js-tools,node-css-loader
Severity: wishlist
node-css-loader autopkgtest fails because
Package: pkg-js-tools,node-css-loader
Severity: wishlist
node-css-loader autopkgtest fails because of a deprecation warning in
stderr. In manual autopkgtest, we can easily add Restrictions:
allow-stderr, provide a way to pass this to autopkgtest-pkg-nodejs
tests too.
--
Pkg-javascript-devel
Package: node-postcss-filter-plugins
Version: 2.0.2-3
Severity: serious
autopkgtest fails with stderr output
postcss.plugin was deprecated. Migration guide:
https://evilmartians.com/chronicles/postcss-8-plugin-migration
This was reported on the team mailing list [1] and tracked in postcss 8
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
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: 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
Package: node-autoprefixer
Version: 10.1.0+~cs11.3.2.0-1
Severity: wishlist
Now node-autoprefixer includes autoprefixer-rails as a component in
source package (for its build directory). We can build
ruby-autoprefixer-rails binary package from the same source and drop
libjs-autoprefixer (there
On Thu, Dec 24, 2020 at 19:50, Paolo Greppi
wrote:
I have run jest in the yarnpkg source tree with:
jest --ci __tests__/
You can add this to debian/tests/pkg-js/test
having this jest.config.js to disable failing tests:
and include this as a patch.
module.exports = {
testURL:
Control: retitle rainloop: ftbfs with node-postcss 8.0
Control: severity -1 serious
On Mon, 28 Sep 2020 21:21:26 +0530 Pirate Praveen
wrote:
>
> node-postcss 8.x will be uploaded to unstable when node-css-loader is
> ready (there is already an upstream pull request and hopef
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
Control: tags -1 pending
On Tue, 22 Dec 2020 16:25:36 +0100 Andreas Beckmann
wrote:
> debian/autoprefixer.js → dist/autoprefixer.js...
> [!] Error: Could not load path (imported by
./../usr/share/nodejs/postcss/lib/map-generator.js): ENOENT: no such
file or directory, open 'path'
> Error:
Control: block -1 by 977900
Control: tag 977900 help
On Sat, 19 Dec 2020 23:21:20 +0530 Pirate Praveen
wrote:
> I'd like to update css-loader to latest upstream release/postcss 8
> transition before I work on this.
node-postcss 8 transition is blocked by an ftbfs bug in
node-autopr
Package: node-schema-utils
Version: 3.0.0-3
Severity: important
schema-utils mentions "@types/json-schema": "^7.0.6" as a dependency in
its package.json but it is not available in debian.
It should probably be added to node-json-schema and added as a
dependency to node-schema-utils.
--
On Wed, Dec 23, 2020 at 16:06, Jonas Smedegaard wrote:
memfs? Is Nodejs module "memfs" in Debian, or are you talking about
something else here?
memfs is used by compression-webpack-plugin for tests, but it is not
yet packaged.
--
Pkg-javascript-devel mailing list
Package: webpack,node-compression-webpack-plugin
Version: 4.43.0-6
Severity: serious
To reproduce this issue,
run
jest --ci test/CompressionPlugin.test.js
in node-compression-webpack-plugin
● CompressionPlugin › should work and show compress assets in stats
TypeError: callback must be a
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
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
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 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, 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, 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
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.
--
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]
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:
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: 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 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
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 17:28, Jonas Smedegaard wrote:
Package: jest
Version: 26.6.3+repack+~cs61.38.31-2
Followup-For: Bug #977670
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Control: reoen -1
Control: retitle -1 jest: should explicitly (build-)depend on needed
babel modules
Thanks
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 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
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 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 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
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 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 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
101 - 200 of 992 matches
Mail list logo
