On 1/6/19 4:04 PM, Debian FTP Masters wrote:.
>* Suggests npm - because nodejs must not be blocked by it.
> Closes: #918388.
I don't think this is correct. ruby-rails even has recommends for not
yet packaged dependencies and I don't see it being blocked by that.
signature.asc
Control: reopen -1
On Sun, 06 Jan 2019 10:34:48 + =?utf-8?b?SsOpcsOpbXkgTGFs?=
wrote:
>* Suggests npm - because nodejs must not be blocked by it.
> Closes: #918388.
I don't think this reasoning is correct. gitlab recommends gitaly with
the expectation that gitaly andd gitlab could
On 2018, നവംബർ 26 2:01:18 AM IST, Jonas Smedegaard wrote:
>Please note that packaging multiple major versions of Nodejs packages
>is
>unusual in Debian. You might want to hear the opinions of others in
>the
>team as well. My reason for suggesting it here is that we are close to
>
>freeze -
On 11/22/18 4:47 PM, Paolo Greppi wrote:
> Hi team,
>
> does anybody know why has node-babel-plugin-transform-inline-imports-commonjs
> originally uploaded to NEW here:
> https://alioth-lists.debian.net/pipermail/pkg-javascript-devel/2018-April/025812.html
> been marked for rejection here:
>
On 11/22/18 5:12 PM, Paolo Greppi wrote:
> Hi team,
>
> node-v8-compile-cache originally uploaded to NEW here:
> https://alioth-lists.debian.net/pipermail/pkg-javascript-devel/2018-April/025959.html
> has been marked for rejection here:
> https://wiki.debian.org/Javascript/Nodejs/NEW
> and
On 2018, നവംബർ 22 9:19:51 PM IST, Paolo Greppi wrote:
>Hi, I have packaged node-tar-fs:
>https://salsa.debian.org/js-team/node-tar-fs
>
>I am Cc-ing the ITP.
>
>Please someone sponsor the upload.
I think this is another candidate for embedding (no build steps required, not
depended on by
On 11/26/18 8:25 PM, Paolo Greppi wrote:
> The file names are crazy ! is this the way the Debian JavaScript Maintainers
> team wants to go ?
> If you are brave, generate the debian/watch for npm and try running uscan on
> it ...
I prefer to use this approach which is much cleaner and manageable
On 1/8/19 12:51 PM, wrote:
> Hi,
>
> anyone using node-yn ? Instead of fixing it i'd rather remove it (it
> looks pretty useless to me).
This is a dependency of yarn. Paolo can comment whether he wants to fix
or remove.
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=886843
signature.asc
Control: severity -1 important
On Wed, 2 Jan 2019 10:57:31 +0100 Ruben Undheim
wrote:
> Bumped the severity since now nodejs 10 is in unstable.
I don't think this warrants an rc bug. It is only a warning and does not
affect npm functionality or violates any policy. Serious bugs are for
packages
On 2019, ജനുവരി 12 1:56:41 PM IST, Paolo Greppi wrote:
>node-js-beautify is kept out of buster by two RC bugs (BTW I guess they
>could be merged ?)
>https://bugs.debian.org/60
>https://bugs.debian.org/888903
>
>this in turn will keep out:
>node-postcss
>node-postcss-modules-values
On Mon, 24 Dec 2018 10:33:48 +0100 Ralf Jung wrote:
>
> COMP_WORDBREAKS=${COMP_WORDBREAKS/=/}
>
> Please remove that line, or otherwise stop breaking unrelated packages.
>
I don't see such a line here.
https://salsa.debian.org/js-team/npm/blob/master/lib/utils/completion.sh
May be that came
Package: node-caniuse-lite
version: 1.0.3915+dfsg-1
severity: grave
Justification: Makes it unusable
Control: block 837463 by -1
Control: tag -1 help
When trying to build autoprefixer.js which build depends on
node-caniuse-lite, I got this error and upon inspection I found
data/features
On Tue, Jan 8, 2019 at 9:41 PM, Paolo Greppi
wrote:
While updating node-braces from 2.0.2 to 2.3.1, I found that the
node-split-string version that we have in debian (6.0.0-1) breaks it
(it only works with 3.0.2).
To see how it breaks it (779/944 tests fail), you can have a look at
a
On 2018, ഡിസംബർ 29 12:29:12 AM IST, Jonas Smedegaard wrote:
>Quoting Pirate Praveen (2018-12-28 19:19:12)
>> When trying to build autoprefixer.js which build depends on
>> node-caniuse-lite, I got this error and upon inspection I found
>> data/features directory is missing.
On 9/8/18 8:26 PM, Ross Gammon wrote:
> https://salsa.debian.org/js-team/npm/wikis/home
npm has a dependency on node-readable-stream, but it is not used
anywhere. If at all we need to backport, it will pull in
node-string-decoder and babel-polyfill and whole babel.
I have removed the dependency
On 9/12/18 11:39 PM, Pirate Praveen wrote:
> I have removed the dependency and pushed to git, but autopkgtest is
> failing. Can someone help me figure out the root cause? We should be
> able to replace any readable-stream usage by require("stream") instead.
I had to remove the
On 9/13/18 1:05 PM, W. Martin Borgert wrote:
> Control: block 907515 by 843951
>
> jingle-session seems to need at least async 2.5.0
>
> Please consider packaging a recent release, thanks!
I think it is harder to update async because of its build dependency on
closure-compiler. But neo-async is a
Control: fixed -1 5.8.0+ds-1
On Thu, 05 Jan 2017 22:16:38 +0100 Salvatore Bonaccorso
wrote:
> the following vulnerability was published for npm.
>
> CVE-2016-3956[0]:
> | The CLI in npm before 2.15.1 and 3.x before 3.8.3, as used in Node.js
> | 0.10 before 0.10.44, 0.12 before 0.12.13, 4 before
On Tue, 24 Jul 2018 08:46:42 +0200 Matthias Urlichs
wrote:
> Package: npm
> Version: 5.8.0+ds-1
> Severity: minor
>
> npm WARN npm npm does not support Node.js v10.4.0
> npm WARN npm You should probably upgrade to a newer version of node as we
> npm WARN npm can't make any promises that npm will
Control: fixed -1 5.8.0+ds3-1
On Thu, 19 Jul 2018 12:16:08 +0530 Pirate Praveen
wrote:
> Control: forcemerge 904071 -1
>
> pravi@andhaka:/tmp/lirc$ npm install --production lirc
It is working now.
pravi@nishumbha:/tmp$ npm install --production lirc
npm WARN deprecated coffee-scri
Control: fixed -1 5.8.0+ds-1
On Sat, 15 Aug 2015 13:25:50 -0600 Anthony Fok wrote:
> There is a fix landed to the completion script in d7271b8 [2]
> – the lib/utils/completion.sh included in the tree at that
> version (which will be part of the next npm@2 release,
> coming out later tonight as
Package: npm2deb
version: 0.2.8-1
severity: wishlist
node-tar embeds some dependencies as components [1] and uses
pkg-components to build. It would be great if npm2deb can automate this
step.
For example,
npm2deb add minizlib
should create debian/components/minizlib and populate the files inside
On 16/09/18 5:10 PM, Ross Gammon wrote:
> Hmm. No ideas for bluebird here really, other than bundling a pre-built
> acorn npm node_module style.
Ashutosh (https://github.com/juggernaut451) is trying to replace
bluebird with ES6 native promise (though it will be slower).
> What is the hold up
Control: tags -1 help
chownr 1.1 will now use fs.lchown if available, but we will have to wait
till nodejs 10.6 is available for the actual fix. So I will keep this
bug open.
But chownr 1.1 tests are currently failing so help is welcome.
signature.asc
Description: OpenPGP digital signature
--
On 2018, സെപ്റ്റംബർ 16 5:16:39 PM IST, Pirate Praveen
wrote:
>> What is the hold up with rollup? I was looking into rollup/acorn in
>> Ubuntu, and things have got very messy there. None of them will build
>> without the right version of each other. It looks like a messe
---+
Unpack source
-
Format: 3.0 (quilt)
Source: node-dashdash
Binary: node-dashdash
Architecture: all
Version: 1.14.1-1
Maintainer: Debian Javascript Maintainers
Uploaders: Pirate Praveen
Homepage: https://github.com/trentm/node-dashdash#readme
Standards-V
On Wed, 25 Apr 2018 15:34:25 +0200 Paolo Greppi
wrote:
> I am OK with moving the repo from collab-maint to salsa and trying a team
> upload.
> Unless the previous uploaders want to take action.
I'm planning to update request now. I have already moved the repo to
salsa under js-team. I'm
On 2018, സെപ്റ്റംബർ 18 2:57:36 AM IST, "W. Martin Borgert"
wrote:
>Hi Jonas, hi team,
>
>I can't find node-uuid on salsa, and collab-maint is dead.
>
>Therefore:
>
> - Is it OK, if I just create the git repo in the js-team space
> using the versions 1.4.0-1 (oldstable, stable) and 1.4.7-5
>
package: npm2deb
version: 0.2.8-1
severity: grave
justification: fails to perform its core function of creating debs
npm2deb create @ava/write-file-atomic
Traceback (most recent call last):
File "/usr/bin/npm2deb", line 7, in
sys.exit(main(sys.argv))
File
Hi team,
I started getting involved in JavaScript team to keep diaspora and gitlab
packages in main.
Gitlab was included in stretch but it is proposed to be removed from buster. [1]
Since it won't be in buster, it can't be in -backports as well, leaving only
unstable. Some people are using
On വെ, ജനു 25, 2019 at 10:22 രാവിലെ, Paolo Greppi
wrote:
Hi, the package node-yarnpkg is ready since a couple of weeks:
https://alioth-lists.debian.net/pipermail/pkg-javascript-devel/2019-January/030472.html
I haven't received any feedback, but from my testing it seems to work
in sid and
On 2019, ജനുവരി 24 7:46:32 PM IST, Xavier wrote:
>Hi all,
>
>I try to write a package that could be called by autodep8 to have a
>"Testsuite: pkg-js" instead of writing debian/tests/* files
>
>Skeleton is pushed in node-combined-stream branch "pkg-js"
>
>What maintainer has to do:
> * in
On Thu, Mar 21, 2019 at 5:58 AM, "Giuseppe M. Pereira"
wrote:
Dear js-team,
My name is Giuseppe Pereira and I'm NodeJS Software Architect in
Brazil. I'm contacting you to apply for join on js-team and
collaborate to Debian community.
How may I proceed?
Hi Guiseppe,
Welcome to
On Tue, Feb 19, 2019 at 2:50 AM, Xavier wrote:
Le 18/02/2019 à 21:20, Xavier a écrit :
Le 18/02/2019 à 20:46, Bastien ROUCARIES a écrit :
Le lun. 18 févr. 2019 à 19:17, Xavier mailto:x.guim...@free.fr>> a écrit :
Le 18/02/2019 à 17:46, Pirate Praveen a
On Tue, Feb 19, 2019 at 1:55 AM, Paul Gevers wrote:
Hi Pirate,
On 17-02-2019 11:51, Pirate Praveen wrote:
Thanks Paul for testing. The missing dependencies were treated as
external dependencies by rollup (webpack would give an error), would
have worked in node, but not in browser. I
On Sat, Mar 2, 2019 at 12:17 AM, Xavier wrote:
Le 01/03/2019 à 19:04, Paolo Greppi a écrit :
I have given signal-desktop a first look.
In terms of dependencies, apart from electron (ehm...) this is what
I
found:
- to be updated:
1. node-chalk: 2.3.0 -> 2.4.1
2. node-espree:
On വ്യാ, ഫെബ്രു 21, 2019 at 6:18 വൈകു, Paul
Gevers wrote:
Hi
On 21-02-2019 13:34, Pirate Praveen wrote:
I have uploaded 2.7.3 to unstable
Thanks a lot. The cacti package already depends on it for several
days.
May be not uploaded yet?
$ reverse-depends libjs-chartjs
Reverse-Depends
On Fri, Nov 23, 2018 at 3:30 AM, Thorsten Alteholz
wrote:
Hi
the initial notes for this package are:
- initial release takes over packages
Because the original package was not built from source (this replaces
the original package built from source, I'm also uploader of the
original
On Thu, Mar 14, 2019 at 5:25 PM, Pirate Praveen
wrote:
On Fri, Nov 23, 2018 at 3:30 AM, Thorsten Alteholz
wrote:
Hi
the initial notes for this package are:
- initial release takes over packages
Because the original package was not built from source (this replaces
the original
On 2019, മാർച്ച് 18 2:33:00 AM IST, Ximin Luo wrote:
>On Thu, 08 Mar 2018 17:53:27 + Ghislain Vaillant
> wrote:
>I had an attempt at this, but it is getting a bit hairy and I think it
>may be time to call it quits. My recommendation is for jupyter-notebook
>to patch out this functionality
On ഞാ, ജനു 13, 2019 at 6:30 വൈകു, Thorsten Alteholz
wrote:
Hi,
the MPLv2 License:-block does not seem to contain the MPLv2 license
text.
Fixed and reuploaded.
Thanks!
Thorsten
===
Please feel free to respond to this email if you don't understand why
your files were rejected,
On Sun, Feb 17, 2019 at 2:47 AM, Paul Gevers wrote:
Hi,
On 15-02-2019 07:46, Pirate Praveen wrote:
Thanks Jonas for the confirmation. I have uploaded 2.7.3 to
experimental. Since browserify is not available in the archive, I
have
used rollup to build the umd bundle. Please review, test
On Thu, 14 Feb 2019 11:57:31 +0100 Jonas Smedegaard wrote:
> Quoting Pirate Praveen (2019-02-14 11:04:03)
> > On Sat, 21 Apr 2018 12:24:49 +0100 Federico Ceratto
> > wrote:
> > > The package has not been updated since 2015. Can you please upload the
> > >
On Mon, Feb 18, 2019 at 11:29 AM, Xavier wrote:
- node-lodash-packages:
- #873016: not preferred form for source: Should be built from
node-lodash
I have fixed it locally, I will upload soon.
--
Pkg-javascript-devel mailing list
On Mon, Feb 18, 2019 at 5:57 PM, Xavier wrote:
I think we should make a ROM-RM to src:node-lodash-packages
Only after this version migrates to testing, else it will be blocked by
freeze as new binary package.
--
Pkg-javascript-devel mailing list
On Thu, Feb 14, 2019 at 10:50 PM, Xavier wrote:
- node-mocha: #921798: FTBFS (Module not found: Error: Recursion in
resolving)
I tried to use rollup instead of webpack (in rollup branch), it builds
fine, but will not work in a browser (should be enough for node). If we
cannot fix thr
On Sat, 21 Apr 2018 12:24:49 +0100 Federico Ceratto
wrote:
> The package has not been updated since 2015. Can you please upload the
> latest release? (Currently 2.7.2)
gitlab was locked to 1.0.2, but they have also moved to 2.7.2 so I will
update soon. Can someone check if python3-ontospy is
On ചൊ, ഫെബ്രു 12, 2019 at 2:49 വൈകു, Olaf van
der Spek wrote:
Op di 12 feb. 2019 om 10:13 schreef Pirate Praveen
:
On ചൊ, ഫെബ്രു 12, 2019 at 2:34 വൈകു, Olaf
van
der Spek wrote:
> Could npm 6 be packaged?
We won't be able to get it into buster (soft freeze starting today),
2019
On ചൊ, ഫെബ്രു 12, 2019 at 2:34 വൈകു, Olaf van
der Spek wrote:
Could npm 6 be packaged?
We won't be able to get it into buster (soft freeze starting today),
but we can try for buster + 1 or possibly buster-backports.
--
Pkg-javascript-devel mailing list
On ചൊ, ഫെബ്രു 12, 2019 at 2:59 വൈകു, Olaf van
der Spek wrote:
Op di 12 feb. 2019 om 10:25 schreef Pirate Praveen
:
> npm 6 has been available for some time..
>
If that introduce any rc bugs, there won't be enough time to fix it
and
I don't want to risk it at this point.
Makes
On വ്യാ, ഫെബ്രു 7, 2019 at 3:48 വൈകു, Jonas
Smedegaard wrote:
Quoting Pirate Praveen (2019-02-07 09:33:33)
This was working fine before, I think its breaking now with nodejs
10
(guess because of reference to buffer in the error and remembering
some discussions around it).
Can someone
Hi,
This was working fine before, I think its breaking now with nodejs 10
(guess because of reference to buffer in the error and remembering some
discussions around it).
Can someone help with this error? I tried adding node-buffer as build
dependency, but that did not change anything.
On വ്യാ, ഫെബ്രു 7, 2019 at 5:12 വൈകു, Jonas
Smedegaard wrote:
Quoting Pirate Praveen (2019-02-07 12:18:59)
On വ്യാ, ഫെബ്രു 7, 2019 at 3:48 വൈകു,
Jonas Smedegaard wrote:
Quoting Pirate Praveen (2019-02-07 09:33:33)
This was working fine before, I think its breaking now with nodejs
10
On ശ, ജനു 26, 2019 at 12:02 രാവിലെ, Dhanesh B.
Sabane wrote:
Hello Debian JS maintainers,
I've prepared the Debian package of a Node module - d3-fetch. It
provides parsing on top of the Fetch standard.[1] The package was
tested on sbuild and was successfully built. It is also
On Wed, 13 Feb 2019 20:52:54 +0100 Xavier wrote:
> This outdated version of gulp depends on (at least) outdated
> node-vinyl-fs and node-first-chunk-stream and unpackaged
> node-glob-watcher. That's why tests fail, this reveals that
> "auto-rebuild" feature is unusable. I hope nothing else is
-buildpackage: info: source package node-postcss
dpkg-buildpackage: info: source version 6.0.23-1
dpkg-buildpackage: info: source distribution unstable
dpkg-buildpackage: info: source changed by Pirate Praveen
dpkg-buildpackage: info: host architecture amd64
dpkg-source --before-build .
fakeroot debian
Hi,
I just uploaded gulp 4 to experimental. I had to embed about 50+ node
modules in it (plus many more in node-vinyl-fs). I have left one
lintian error about source missing since there is no easy way to
exclude it (see #929805).
Please help test it (though there is no urgency as we are in
package: uglifyjs.terser
version: 3.14.1-1
severity: grave
justification: it does not work at all
Sample repo https://salsa.debian.org/gi-boi-guest/node-d3-fetch
Also tried in https://salsa.debian.org/js-team/node-d3-scale-chromatic
with same error when trying to minimize
On Fri, Nov 23, 2018 at 3:30 AM, Thorsten Alteholz
wrote:
Hi,
please take care of errors from lintian.
Fixed and reuploaded.
Dependency node-foreach does not seem to be available yet?
This was in NEW but rejected in favour of using lodash.foreach from
node-lodash-packages. Applied
: source changed by Pirate Praveen
dpkg-buildpackage: info: host architecture amd64
dpkg-source --before-build .
fakeroot debian/rules clean
dh clean --with nodejs
debian/rules override_dh_auto_clean
make[1]: Entering directory
'/home/pravi/forge/debian/git/js-team/node-babel'
dh_auto_clean
make
On Sat, Jun 1, 2019 at 12:36 PM, Xavier wrote:
Hello,
seems good to me. Some things:
Though it does not really work when tried with node-babel, tracking it
here #929829
* node-vinylfs
- build is not reproductible using
node-vinyl-fs_3.0.3.orig-is-utf8.tar.gz added to
On Sat, Jun 1, 2019 at 4:33 PM, Pirate Praveen
wrote:
yes, but there is no easy way to filter it. I have reported a bug.
see #929831
--
Pkg-javascript-devel mailing list
Pkg-javascript-devel@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript
On 2019, ജൂൺ 6 11:00:16 AM IST, Xavier wrote:
>My reducejs tool gives a new analysis:
> * downgraded modules to embed
> - process-nextick-args : 2.0.0 => 1.0.7
This is handled by a patch.
https://salsa.debian.org/js-team/node-gulp/blob/master/debian/patches/update-process-nextick-args.patch
On 2019, ജൂൺ 13 11:19:51 AM IST, Xavier wrote:
>Le 13/06/2019 à 07:35, Pirate Praveen a écrit :
>>
>>
>> On 2019, ജൂൺ 13 10:06:25 AM IST, Xavier wrote:
>>> Le 13/06/2019 à 06:32, Pirate Praveen a écrit :
>>>> Control: severity -1 grave
>>>&g
On Sun, 16 Jun, 2019 at 5:34 PM, Pirate Praveen
wrote:
While we are at it, we have provide an es module entry point as well.
See #930591
I tried to use the upstream provided build script which uses rollup (it
is pushed to rollup branch on salsa), but it failed with this error
On Sun, 13 Jan, 2019 at 9:30 PM, Thorsten Alteholz
wrote:
Hi,
the qunit license block in your debian/copyright seems to be wrong.
Fixed in 4.2.2+dfsg-1
Please also add some more attributions.
Fixed in 4.2.2+dfsg-2 (missed this comment and it went to NEW before I
could rm it).
Package: node-ajv-keywords
version: 2.1.0-1
severity: wishlist
Control: block -1 by 930558
This update is needed for node-schema-utils 1.0 (which is required to
update node-cache-loader 2.x)
--
Pkg-javascript-devel mailing list
Pkg-javascript-devel@alioth-lists.debian.net
package: node-cache-loader
version: 1.2.2-1
severity: wishlist
Control: block 930404 by -1
This is required for gitlab 11.10.5.
--
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-ajv
version: 5.0.0-1
severity: wishlist
Control:block -1 by 908637
ajv 6 is a build dependency of ajv-keywords 3 (which is a dependency of
schema-utils 1.0)
--
Pkg-javascript-devel mailing list
Pkg-javascript-devel@alioth-lists.debian.net
On 2019, ജൂൺ 10 11:33:29 PM IST, Paolo Greppi wrote:
>If I build manually the UMD version using the same command as in
>debian/rules:
>
>NODE_PATH=debian/node_modules/ rollup -m -c debian/rollup-umd.js
>
>I get this:
>
>/home/paolog/Sviluppo/debian/vue-router.js/src/index.js →
Package: node-recast
version: 0.16.1-1
severity: wishlist
Control: block 930265 by -1
recast type definitions are required for building
node-rollup-plugin-invariant (I have started working on the update).
--
Pkg-javascript-devel mailing list
Pkg-javascript-devel@alioth-lists.debian.net
package: src:typescript-types
version: 20190209-1
severity: wishlist
If there is an agreement in principle, I can help with implementing it.
See node-gulp for an example of using multiple tarballs.
--
Pkg-javascript-devel mailing list
Pkg-javascript-devel@alioth-lists.debian.net
package: node-ast-types
version: 0.11.7-1
severity: wishlist
Control: block 930266 by -1
While trying to update node-recast to 0.18, tsc throws this error
lib/comments.ts(2,24): error TS7016: Could not find a declaration file
for module 'ast-types'. '/usr/lib/nodejs/ast-types/main.js'
package: node-esprima
version: 4.0.1+ds-1
severity: wishlist
Control: block 930267 by -1
tsc throws this error,
test/ecmascript.ts(2,31): error TS7016: Could not find a declaration
file for module 'esprima'. '/usr/lib/nodejs/esprima/dist/esprima.js'
implicitly has an 'any' type.
Try `npm
Control: block -1 by 929829
It has these errors and more, so we will need babel 7 to proceed.
test/ecmascript.ts(6,29): error TS2307: Cannot find module '@babel/types'.
test/typescript.ts(4,66): error TS2307: Cannot find module '@babel/parser'.
types/esprima.d.ts(7,19): error TS2384: Overload
Package: npm2deb
Version: 0.3.0-1
severity: wishlist
It should use apt-file find to list out packages embedding the module.
This can help determine the module as a candidate for embedding easily.
$ npm2deb search source-map-url
Looking for similar package:
node-css (2.1.0-2) (unstable)
package: node-typescript
version: 3.4.5-1
severity: important
Now every package that uses tsc is having to add symlink for system
modules to local node_modules directory. See node-xterm for an example,
On Sun, 23 Sep 2018 20:06:05 +0530 Pirate Praveen
wrote:
> Please add type definitions for @types/glob.
@types/estree is required by node-ast-types
signature.asc
Description: OpenPGP digital signature
--
Pkg-javascript-devel mailing list
Pkg-javascript-devel@alioth-lists.debian.net
ht
Package: libjs-bootstrap4
severity: wishlist
version: 4.3.1+dfsg2-1
gitlab uses webpack and expects bootstrap node module. Please provide
this in addition to libjs.
--
Pkg-javascript-devel mailing list
Pkg-javascript-devel@alioth-lists.debian.net
Package: node-compression-webpack-plugin
version: 1.1.10-2
severity: wishlist
Control: block 930404 by -1
Control: block -1 by 930561
This update is required for gitlab 11.10.5
--
Pkg-javascript-devel mailing list
Pkg-javascript-devel@alioth-lists.debian.net
On Tue, 11 Jun, 2019 at 12:18 PM, Paolo Greppi
wrote:
On 11/06/19 08:03, Pirate Praveen wrote:
I think rollup-plugin-commonjs will also work without extra options,
see node-d3-fetch.
rollup-plugin-commonjs is already there in the upstream rollup config:
https://salsa.debian.org/js-team
package: pkg-js-tools
version: 0.5
severity: wishlist
Many of the node-d3-* modules have package.json#main and other packages
"import" these. So we should have a test to check if import works like
we have require test.
We may need to use node --experimental-modules or npmjs.com/esm node
Control: tag -1 help
On Tue, 25 Jun, 2019 at 1:49 PM, Pirate Praveen
wrote:
While looking for something else in package.json, I realized, there
was a line excluding node_modules and there was two places I needed
to update. With the following patch, webpack is successful.
Now
Control: tag -1 -help
On Tue, 25 Jun, 2019 at 1:22 PM, Pirate Praveen
wrote:
The easiest fix would be updating node-d3-format, but it is not team
maintained any more (result of an accidental hijack from me). Other
option would be to fix webpack configuration. Hope someone can help
here
Control: tag -1 help
On Sat, 08 Jun 2019 20:48:32 +0500 Pirate Praveen
wrote:> This library is a dependency of
gitlab. Since it uses babel and webpack
> to generate ES5 code, it is not suitable for embedding.
With node-d3 in NEW/salsa (#801765), I get this error. d3-format and
d3
On Tue, 25 Jun, 2019 at 3:07 PM, Pirate Praveen
wrote:
Now there is another error (tried replacing commonjs2 with commonjs,
also tried with nodejs 12),
dh_auto_test --buildsystem=nodejs
/usr/bin/node -e require\(\".\"\)
/<>/dist/dagre-d3.core.js:950
function
On Tue, 25 Jun, 2019 at 3:13 PM, Pirate Praveen
wrote:
Same error when changing package.json#main to dist/dagre-d3.js (umd
format).
To confirm it is not a browser only library, I downloaded the
dagre-d3-renderer dist.tarball from npmjs.com and the require command
succeeds
package: node-chart.js
severity: important
version: 2.7.3+dfsg-3
webpack is able to find other packaged modules like autosize,
brace-expasion etc so it is likely a bug with node-chart.js
ERROR in ./pages/projects/graphs/charts/index.js
Module not found: Error: Can't resolve 'chart.js' in
On 2019, ജൂൺ 20 2:07:38 PM IST, Paolo Greppi wrote:
>nodejs -e 'dsv = require("."); console.log(dsv.csvFormat([{date: new
>Date(2018, 0, 1)}]));'
>TZ='UTC' nodejs -e 'dsv = require(".");
>console.log(dsv.csvFormat([{date: new Date(2018, 0, 1)}]));'
>TZ='EST' nodejs -e 'dsv = require(".");
On 2019, ജൂൺ 20 5:08:24 PM IST, Xavier wrote:
>Hello,
>
>there is something wrong with your patch:
>W: node-terser source: binaries-have-file-conflict node-terser
>uglifyjs.terser usr/lib/nodejs/terser/dist/bundle.js
>
>Your link overrides a regular file
Only node-terser should include this
package: pkg-js-tools
version: 0.5
severity: important
In node-d3-queue salsa master, autopkgtest is failing. This is because
the tests expects more files than 'test' directory to be present
locally. In gem2deb, only lib directory is renamed to force using
installed library. I think the same
package: node-acorn
version:
6.0.2+20181021git007b08d01eff070+ds+~0.3.1+~4.0.0+~0.3.0+~5.0.0+ds+~1.6.1+ds-1
severity: wishlist
Please add Breaks: webpack (<< 4.28.3~) as node-acorn 6 gets installed
otherwise in experimental (experienced when trying to build
node-dagre-d3-renderer in salsa).
Control: severity -1 grave
On 2019, ജൂൺ 13 12:20:23 AM IST, Xavier wrote:
>Fixed in salsa. Do you think this requires an unblock ?
Yes
--
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 2019, ജൂൺ 13 10:06:25 AM IST, Xavier wrote:
>Le 13/06/2019 à 06:32, Pirate Praveen a écrit :
>> Control: severity -1 grave
>>
>> On 2019, ജൂൺ 13 12:20:23 AM IST, Xavier wrote:
>>> Fixed in salsa. Do you think this requires an unblock ?
>>
>>
Package: node-diff
version: 1.4.0~dfsg-1
severity: wishlist
Control: block 930404 by -1
We'd like to use packaged version of diff node module to move gitlab
back to main (currently it is installed using yarn in postinst and
hence gitlab is in contrib). I'd be happy to help with the update.
Package: node-vue-resource
Version: 1.5.1-1
severity: grave
Control: block 930404 by -1
When trying to use packaged version of node-vue-resource, Web Console
shows this error. UI elements just show the spinning circle forever.
Upstream is using rollup based build system and we converted it to
On Mon, 17 Jun, 2019 at 1:51 PM, Pirate Praveen
wrote:
set -e;mkdir -p stage2/;cp -r src stage2/;cp -r browser stage2/;cp -r
bin stage2/;cp package.json stage2/;cp rollup.config.js stage2/
cd stage2/ && BABEL_PRESET=es2015 node ../stage1//bin/rollup
--verbose -c
[!] TypeErro
-buildpackage: info: source changed by Pirate Praveen
dpkg-source --before-build .
dpkg-buildpackage: info: host architecture amd64
fakeroot debian/rules clean
dh clean
debian/rules override_dh_auto_clean
make[1]: Entering directory '/<>'
rm -rf dist
rm -f bin/rollup
rm -rf stage*
make[1]: L
Package: rollup
version: 0.50.0-6
severity: wishlist
Many packages in the archive (for example vue.js) needs a newer version
of rollup to build. I think we will need to do the updates in many
steps to reach the latest version as rollup supports building only with
only one or two versions
On 2019, മേയ് 8 11:30:10 AM IST, Bastian Blank
wrote:
>
>While the (compiled) javascript part is quite large (8k), this split is
>only
>done to save one dependency (either ruby or nodejs) from being
>installed.
>
>We've talked about this.
Last time we talked about it, I asked for an
101 - 200 of 992 matches
Mail list logo
