Package: vue.js
Version: 2.5.17+dfsg-1
Severity: important
Control: tags -1 patch
When building with webpack 4 in experimental, build failed with error.
Error: webpack.optimize.UglifyJsPlugin has been removed, please use
config.optimization.minimize instead.
Same issue is fixed in node-axios
Package: node-trust-json-document
Version: 0.1.4~dfsg-4
Severity: important
When building with webpack 4 currently in experimental, build fails with this
error.
webpack -d --output-filename json-document.js Invalid configuration object.
Webpack has been initialised using a configuration
Package: node-node-forge
Version: 0.8.5~dfsg-1
Severity: important
Control: tags -1 patch
While trying build your package with webpack 4.7 in experimental, build failed
with this error.
Error: webpack.optimize.UglifyJsPlugin has been removed, please use
config.optimization.minimize instead.
Package: pkg-js-tools
Version: 0.8.6
Severity: wishlist
I was trying to pkg-js-tools auto install option with
node-fuzzaldrin-plus but it did not work as it had libjs-fuzzaldrin-plus
also as a binary package. The files got copied to debian/tmp and the
final deb file did not these files.
I
$ apt-file list node-uglifyjs-webpack-plugin
node-uglifyjs-webpack-plugin:
/usr/lib/nodejs/uglifyjs-webpack-plugin/dist/index.js
node-uglifyjs-webpack-plugin:
/usr/lib/nodejs/uglifyjs-webpack-plugin/lib/post_install.js
node-uglifyjs-webpack-plugin:
Package: node-terser
Version: 4.1.2-3
Severity: wishlist
terser is a drop in replacement for uglifyjs. It'd be nice to provide the same
command using alternatives mechanism (/etc/alternatives) to transparently
update to terser from uglifyjs. If we do, please add Provides: uglifyjs too.
--
Sent
Package: yarnpkg
Version: 1.13.0-1
Severity: important
Webpack 4.7.0 is available in experimental. I'd like to upload it to
unstable as soon as possible. Please make sure yarnpkg works with
webpack 4.
See https://wiki.debian.org/Javascript/Nodejs/Webpack4 for more
information.
--
On 2019-07-31 00:33, Julien Puydt wrote:
Hi,
the original report was about shipping the files correctly and fixing
the ES module exports.
For the first part you already committed a fix, and for the later, I
had
a look and the end of dist/magic-string.es.js is:
export { Bundle, SourceMap };
Package: webpack
Version: 4.7.0-1
Severity: grave
Reproducible on node-url-parse and node-axios git master. Though
dpkg-buildpackage works, fails only in sbuild. I wonder if related to
#932659
webpack --config debian/webpack.config.js --output-library=URLParse \
--entry index.js --output
On 2019, ജൂലൈ 30 12:01:19 PM IST, Xavier wrote:
>Hi all,
>
>I continue to improve auto_install. Here is a resume (from doc). Do you
>thinks it's in the right way to provide an auto-installer? (this part
>is
>not published in experimental but ready and with tests on salsa repo)
>
>NB:
On 2019-07-28 17:44, Pirate Praveen wrote:
On 2019, ജൂലൈ 28 9:32:27 PM IST, Pirate Praveen
wrote:
I think all reverse dependencies will need updating as "mode" seems
mandatory.
After adding options like this,
--entry index.js --output build/d3-force.js
And adding mode: 'd
On 2019, ജൂലൈ 29 5:37:42 AM IST, Jonas Smedegaard wrote:
>terser and uglify-js are competing projects.
>
>I am unaware of any conclusive information on either of them being
>superior to the other for all(!) use-cases.
>
>I intend to maintain both projects, unless convinced otherwise.
On 2019, ജൂലൈ 28 9:32:27 PM IST, Pirate Praveen
wrote:
>
>I think all reverse dependencies will need updating as "mode" seems
>mandatory.
After adding options like this,
--entry index.js --outpu
On 2019, ജൂലൈ 28 10:45:47 AM IST, Pirate Praveen
wrote:
>Hi,
>
>All dependencies for webpack 4.0 are ready in experimental or in git.
>Some tests are failing, which needs a closer look. Help is welcome to
>fix test failures. This is possibly a mocha compatibility issue as
>w
On 2019, ജൂലൈ 28 4:53:53 PM IST, Xavier wrote:
>Le 28/07/2019 à 13:08, Xavier a écrit :
>> Le 28/07/2019 à 10:01, Pirate Praveen a écrit :
>>> Package: pkg-js-tools
>>> Version: 0.8.2
>>> Severity: grave
>>>
>>> Reproducible in node-webpack
Package: pkg-js-tools
Version: 0.8.2
Severity: grave
Reproducible in node-webpack master.
dh_auto_configure --buildsystem=nodejs
mkdir node_modules mkdir webpack-cli/node_modules
ln -s ../eslint-scope node_modules/eslint-scope
ln -s ../../eslint-scope
Package: pkg-js-tools
Version: 0.8.2
Severity: important
DEB_BUILD_OPTIONS=nocheck works, but both should be supported. Build options
don't filter build dependencies so we can't use it when circular test only
dependencies prevent builds.
--
Sent from my Android device with K-9 Mail. Please
Package: pkg-js-tools
Version: 0.8.2
Severity: important
This makes a second dpkg-buildpackage to fail because of upstream changes.
--
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
Hi,
All dependencies for webpack 4.0 are ready in experimental or in git. Some
tests are failing, which needs a closer look. Help is welcome to fix test
failures. This is possibly a mocha compatibility issue as webpack needs mocha 3
and we are already on mocha 4.
Once we fix the tests, we
Package: node-anymatch
Version: 3.0.3+~2.0.7-1
Severity: serious
Justification: makes package unusable
Found this while building node-watchpack 1.6
Error: Cannot find module 'normalize-path' Require stack:
- /usr/share/nodejs/anymatch/index.js -
On 2019, ജൂൺ 17 3:36:54 PM IST, Debian FTP Masters
wrote:
>binary:node-immutable is NEW.
>binary:node-immutable is NEW.
>source:node-immutable is NEW.
>node-immutable_3.8.2+dfsg.orig.tar.xz is only available in NEW.
>node-immutable_3.8.2+dfsg.orig.tar.xz is only available in NEW.
>
>Your
On 2019, ജൂലൈ 26 11:50:12 PM IST, Debian FTP Masters
wrote:
>* Revert rollup test: will be done later using node
>--experieantal-modules
It seems both implementations are incompatible right now.
https://github.com/nodejs/help/issues/2081#issuecomment-515723065
So I think rollup test would
Control: severity -1 wishlist
On 2019, ജൂലൈ 28 1:48:56 AM IST, Christoph Schulz
wrote:
>Package: yarnpkg
>Version: 1.13.0-1
>Severity: grave
>Justification: renders package unusable
>
>
>Dear Maintainer,
>
>it seems like the yarnpkg executable is broken somehow.
>
>Please see below for the full
Hi,
While updating webpack to 4.0, I came to know terser is a drop in replacement
for uglify-js and uglify-es (both unmaintained now).
Should we target moving to a single minifier for bullseye?
Advantage is less maintenance (less number of packages to maintain) and it
seems terser is in a
Package: pkg-js-tools
Version: 0.8.2-1
Severity: wishlist
I think we should parse package.json#scripts#build automatically and run build
commands that we understand. Start with babel,
In node-uglifyjs-webpack-plugin has,
babel src -d dist --ignore 'src/**/*.test.js' --copy-files
We can skip
Package: npm2deb
Version: 0.3.0-1
Severity: wishlist
We can add debhelper-compat (= nn) format in control only (remove compat)
instead of keeping that info in 2 files (control and compat)
--
Sent from my Android device with K-9 Mail. Please excuse my brevity.--
Pkg-javascript-devel mailing
Package: npm2deb
Version: 0.3.0-1
Severity: wishlist
Currently embedding a module involves updating watch, gbp.conf.
It'd be nice to have "npm2deb embed module@version" option to automate this.
Watch file should lock it to major version for modules with version >= 1.0 and
major.minor for
On Thu, 25 Jul 2019 13:08:24 +0530 Pirate Praveen
wrote:
Fixed in git, but still node esm loader can't find the export.
Reported as a bug against node upstream.
--
Sent from my Android device with K-9 Mail. Please excuse my brevity.--
Pkg-javascript-devel mailing list
Pkg-javascript-devel
package: node-rollup-plugin-typescript
Version: 0.8.1-1
Severity: serious
Justification: the package is not usable
Got same error in node-locate-character and node-sourcemap-codec (tried with
node-rollup-plugin-typescript 1.0.0 in git as well and got same error)
node-sourcemap-codec$ rollup -c
On 2019, ജൂലൈ 26 7:04:07 PM IST, "Jérémy Lal" wrote:
>It seems several packages are installing files into
>"rollup-plugin-typescript".
I did not understand this, can you specify which packages you are referring to
here ?
>In this case, all such packages should agree upon the place where the
Package: node-tslib, node-typescript, node-rollup-plugin-typescript
Severity: serious
Justification: breaks node-rollup-plugin-typescript
In last upload of node-tslib, location was changed from /usr/lib/nodejs to
/usr/share/nodejs. This broke node-rollup-plugin-typescript as it was trying to
With node-rollup-plugin-typescript built from git master,
I get this error, I tried to symlink /usr/share/nodejs/tslib to node_modules
but got the same error. I guess we need to pass the path to node-resolve plugin
in rollup.config.js
$ rollup -c
[!] Error:
Package: node-rollup-plugin-typescript
Version: 0.8.1-1
Severity: wishlist
Control: block 932962 by -1
node-sourcemap-codec require newer version of this package.
--
Sent from my Android device with K-9 Mail. Please excuse my brevity.--
Pkg-javascript-devel mailing list
Control: reopen -1
On 2019, ജൂലൈ 26 12:45:05 AM IST, Debian Bug Tracking System
wrote:
>This is an automatic notification regarding your Bug report
>which was filed against the node-locate-character: package:
Generated 'dist' directory is not installed (already fixed in git).
But it seems
On 2019, ജൂലൈ 26 1:29:43 PM IST, Pirate Praveen
wrote:
>
>
>On 2019, ജൂലൈ 25 4:10:32 PM IST, Pirate Praveen
> wrote:
>>And it works! I was able to build node-d3-time with this version of
>>rollup.
>>
>>Check esm branch on salsa.
>
>I tried changing b
On 2019, ജൂലൈ 25 4:10:32 PM IST, Pirate Praveen
wrote:
>And it works! I was able to build node-d3-time with this version of
>rollup.
>
>Check esm branch on salsa.
I tried changing back require to import for locate-character after shipping ES
module (please build node-locate-ch
On 2019, ജൂലൈ 25 5:02:19 PM IST, Xavier wrote:
>Then we will be sure to have the same rollup than upstream
I asked upstream to support this method, possibly as another module,
https://github.com/rollup/rollup/issues/3007
I need help with handling help.md (disabled right now) since my js
On 2019, ജൂലൈ 25 11:15:50 PM IST, Xavier Guimard wrote:
>Package: pkg-js-tools
>Version: 0.8.1
>Severity: wishlist
>
>When using components in node modules, the best way to use them is to
>install them in node_modules/ directory. However, dpkg-source install
>them at the top source directory
Package: nodejs
Version: 12.1.0~dfsg-1
Severity: important
While trying to run rollup directly as an ES module, with node
--experimental-modules option, we hit an internal error which upstream
confirmed as fixed in 12.7. Please update nodejs so we can update rollup.
See
On 2019, ജൂലൈ 25 5:02:19 PM IST, Xavier wrote:
>Thanks a lot !
>
>Could you build rollup with 2 passes ? First with node, then copy
>package.json, bin/ and dist/ to node_modules/rollup with a link in
>node_modules/.bin ; then rebuild with this rollup
>
>Then we will be sure to have the same
On 2019, ജൂലൈ 25 3:32:04 PM IST, Pirate Praveen
wrote:
>After a lot of trial and error, I got to run rollup directly as an ES
>module. I had to disable help.md loading. I will push this to a new
>branch on salsa.
>
>$ node --experimental-modules bin/src/index.js
On 2019, ജൂലൈ 25 1:35:04 AM IST, Pirate Praveen
wrote:
>
>
>On 2019, ജൂലൈ 25 1:14:27 AM IST, Pirate Praveen
> wrote:
>>
>>
>>On 2019, ജൂലൈ 24 3:09:59 PM IST, Pirate Praveen
>> wrote:
>>>Opened https://github.com/nodejs/node/issues/28835
>>
Package: node-magic-string
Version: 0.25.3-1
Severity: important
Provided magic-string.es.js does not match location mentioned in "module" field
of package.json
With import path changed and directly running ES module in rollup,
$ node --
experimental-modules bin/src/index.js
Package: node-sourcemap-codec
Version: 1.4.5-1
Severity: important
While running rollup directly as ES module,
$ node --experimental-modules bin/src/index.js (node:19295)
ExperimentalWarning: The ESM module loader is experimental.
Package: node-acorn
Version: 5.5.3+ds3-3
Severity: important
When trying to use ES module version of rollup,
$ node --experimental-modules bin/src/index.js (node:19235)
ExperimentalWarning: The ESM module loader is experimental.
Package: node-locate-character:
Version: 2.0.1-3
Severity: wishlist
When trying to use ES module directly in node-rollup, I got this error.
$ node --experimental-modules bin/src/index.js (node:18797)
ExperimentalWarning: The ESM module loader is experimental.
On 2019, ജൂലൈ 25 1:14:27 AM IST, Pirate Praveen
wrote:
>
>
>On 2019, ജൂലൈ 24 3:09:59 PM IST, Pirate Praveen
> wrote:
>>Opened https://github.com/nodejs/node/issues/28835
>
>Upstream confirmed this is a bug and it is fixed already in 12.7.0. Can
>we update nodejs
On 2019, ജൂലൈ 24 3:09:59 PM IST, Pirate Praveen
wrote:
>Opened https://github.com/nodejs/node/issues/28835
Upstream confirmed this is a bug and it is fixed already in 12.7.0. Can we
update nodejs in experimental?
--
Sent from my Android device with K-9 Mail. Please excuse my brev
On 2019, ജൂലൈ 24 3:09:59 PM IST, Pirate Praveen
wrote:
>
>
>On 2019, ജൂലൈ 24 2:45:41 PM IST, Pirate Praveen
> wrote:
>>
>>$ node --experimental-modules bin/src/index.js (node:324)
>>ExperimentalWarning: The ESM module loader is experimental.
On 2019, ജൂലൈ 24 5:21:03 PM IST, Nilesh Patra wrote:
>Well that's odd.
>Do simply calling "node-gyp" from terminal work at all ?
>
>Yes, it does. Calling "gyp" from the terminal works too. However when
>I
>did the changes in build.js scipt (via quilt) and try to build it, I
>get
>the same
On 2019, ജൂലൈ 24 2:45:41 PM IST, Pirate Praveen
wrote:
>
>$ node --experimental-modules bin/src/index.js (node:324)
>ExperimentalWarning: The ESM module loader is experimental.
>internal/modules/cjs/loader.js:817
>internalBind
On 2019, ജൂലൈ 24 2:29:07 PM IST, Pirate Praveen
wrote:
>
>
>On 2019, ജൂലൈ 24 1:34:06 PM IST, Pirate Praveen
> wrote:
>>
>>
>>On 2019, ജൂലൈ 24 4:22:28 AM IST, Xavier wrote:
>>>Final results:
>>>
>>>0.50.0 can build until 0.53.3
>>
On 2019, ജൂലൈ 24 1:34:06 PM IST, Pirate Praveen
wrote:
>
>
>On 2019, ജൂലൈ 24 4:22:28 AM IST, Xavier wrote:
>>Final results:
>>
>>0.50.0 can build until 0.53.3
>>0.51.7 can build until 0.56.3
>>0.56.1 can build until 0.65.2
>>0.58.1 can build
On 2019, ജൂലൈ 24 4:22:28 AM IST, Xavier wrote:
>Final results:
>
>0.50.0 can build until 0.53.3
>0.51.7 can build until 0.56.3
>0.56.1 can build until 0.65.2
>0.58.1 can build until 0.67.2
>0.59.1 can build until 1.12.0
>1.12.0 can build until 1.17.0
>
>So 6 steps needed (4 breaking changes),
On 2019, ജൂലൈ 24 4:22:28 AM IST, Xavier wrote:
>Final results:
>
>0.50.0 can build until 0.53.3
>0.51.7 can build until 0.56.3
>0.56.1 can build until 0.65.2
>0.58.1 can build until 0.67.2
>0.59.1 can build until 1.12.0
>1.12.0 can build until 1.17.0
>
>So 6 steps needed (4 breaking changes),
On 2019, ജൂലൈ 23 6:36:10 PM IST, "Jérémy Lal" wrote:
>> Currently building node-sass gives this error.
>>
>> Error: Cannot find module 'node-gyp/bin/node-gyp.js'
>>
>
>That's another issue.
>node-sass scripts/build.js is completely wrong in its path resolution.
>
What do you suggest as a fix
Package: node-gyp
Version: 3.8.0-6
Severity: important
Now that node modules are installed in /usr/share/nodejs, node-gyp should do
the same.
Currently building node-sass gives this error.
Error: Cannot find module 'node-gyp/bin/node-gyp.js'
--
Sent from my Android device with K-9 Mail.
I was able to reproduce in a clean sid chroot.
Created chroot with debootstrap, chroot to directory, install nodejs, node-y18n
node -e "require('y18n');" internal/modules/cjs/loader.js:583
throw err; ^
On 2019, ജൂലൈ 22 9:34:45 PM IST, Xavier wrote:
>The problem is that uscan provides updated files for component =ignore.
>Then async-done patch fails for example
Check version in the embedded code in master branch package.json and use manual
download for now.
>> Since my laptop is broken I
On 2019, ജൂലൈ 22 6:57:06 PM IST, Xavier wrote:
>Le 22/07/2019 à 12:59, Xavier a écrit :
>> Hi all,
>>
>> current node-help-me is incompatible with node-glob-stream 6. This
>> update fixes the problem but requires node-glob-stream 6.
>> I think we can safely push node-glob-stream 6 from
On 2019, ജൂലൈ 21 8:39:28 PM IST, Xavier wrote:
>Hi all,
>
>node-glob-stream is updated in experimental but version in upstream is
>outdated: enabling tests during build shows that it requires many old
>libraries (see tracker)
>It's also the last package not compatible with should.js 13
On 2019, ജൂലൈ 21 3:17:13 PM IST, Xavier wrote:
>Last rollup (1.17) requires 0.51
No, rollup 1.17 requires rollup 1.16.7 so we will have to take several stages
to update to latest.
https://github.com/rollup/rollup/blob/5d1541a577b06d9004a3533bde672761e5798482/package.json#L105
--
Sent from
On 2019, ജൂലൈ 21 7:34:12 PM IST, Julien Puydt wrote:
>
>What is especially frustrating is that I used to have a setup where my
>tests were actually worth something. Then the harddisk died, and my new
>configuration keeps on failing to detect problems... there must be
>something I didn't set up
On 2019, ജൂലൈ 21 2:08:03 PM IST, Xavier wrote:
>Plan to update rollup:
> * downgrade node-rollup-plugin-commonjs
Yes
>* package rollup@0.52.0 (needed to build recent rollup) in experimental
Its ready in git, need node-immutable in NEW.
> * verify with ci.debian.net API that all builds well
On 2019, ജൂലൈ 21 12:52:00 PM IST, Xavier wrote:
>Hi all,
>
>rollup is broken in upstream due to node-rollup-plugin-commonjs update
>(10.0.1): unable to build. I think the best is to downgrade
>node-rollup-plugin-commonjs in unstable and try these updates in
>experimental
It is really
On 2019, ജൂലൈ 20 4:17:16 PM IST, Nilesh Patra wrote:
>Hi
>While packaging node-mermaid and resolving relevant paths. I experience
>several of these errors:
>
>WARNING in ./src/themes ^\.\/.*\/index\.scss$
>Module not found: Error: Recursion in resolving
>Stack:
>resolve:
Hi,
Historically we did not have the build tools for jquery in the archive, so a
custom build system was created to build libjs-jquery. If there is any change
in upstream build system, it will be hard to update this build system and since
the same build tools used by upstream is now available
On 2019, ജൂലൈ 12 12:34:48 AM IST, Xavier wrote:
>node-buble upgrade needs:
> * acorn: 5.5.3 => 6.2.0
> * acorn-dynamic-import : 3.0.0 => 4.0.0
> * acorn-jsx: 4.1.1 => 5.0.1
>
>So we will have to update:
> * first rollup to break acorn-dynamic-import link
> * second
On 2019, ജൂലൈ 10 8:40:21 PM IST, Xavier wrote:
>Le 10/07/2019 à 14:40, Pirate Praveen a écrit :
>> Package: pkg-js-autopkgtest
>> version: 0.8
>> severity: serious
>>
>> autopkgtest_rollup_src.js → autopkgtest_rollup_dest.js...
>> (!) Generated an empt
Package: pkg-js-autopkgtest
version: 0.8
severity: serious
autopkgtest_rollup_src.js → autopkgtest_rollup_dest.js...
(!) Generated an empty bundle
(!) Unresolved dependencies
https://github.com/rollup/rollup/wiki/Troubleshooting#treating-module-as-external-dependency
d3-zoom (imported by
Package: uglifyjs.terser
Version: 4.1.0-1
Severity: serious
justification: insufficient minimum version breaks the package
If uglify.terser is updated to 4.1.0, node-terser and libjs-terser is
not updated along with it, causing the following error.
uglifyjs.terser dist/d3-zoom.js -o
On 2019, ജൂലൈ 10 3:12:37 PM IST, Pirate Praveen
wrote:
>This upload broke node-webpack and node-buble and that means a large
>number of packages now FTBFS.
>
I think we should revert node-acorn-dynamic-import to 4.0.really.3.0 update,
till we fix node-webpack and node-buble.
--
On 2019, ജൂലൈ 9 10:20:04 PM IST, Debian FTP Masters
wrote:
>
>
>Accepted:
>
>-BEGIN PGP SIGNED MESSAGE-
>Hash: SHA512
>
>Format: 1.8
>Date: Tue, 09 Jul 2019 18:34:17 +0200
>Source: node-acorn-dynamic-import
>Binary: node-acorn-dynamic-import
>Architecture: source all
>Version: 4.0.0-1
On 2019, ജൂലൈ 9 2:12:43 PM IST, Xavier wrote:
>Hello,
>
>pkg-js-autopkgtest launches 2 tests:
> - a `node -e 'require("package")'
> - upstream tests on installed files
>
>is it enough ?
For packages that only provide commonjs/umd modules, that should be enough.
For packages that also provide
[adding Jonas to cc]
On Fri, 21 Jun 2019 08:36:15 +0200 Xavier wrote:
> Le 21/06/2019 à 06:04, Pirate Praveen a écrit :
> >
> >
> > On 2019, ജൂൺ 20 5:08:24 PM IST, Xavier wrote:
> >> Hello,
> >>
> >> there is something wrong with your patch
[adding Jonas to cc]
On Fri, 21 Jun 2019 08:36:15 +0200 Xavier wrote:
> Le 21/06/2019 à 06:04, Pirate Praveen a écrit :
> >
> >
> > On 2019, ജൂൺ 20 5:08:24 PM IST, Xavier wrote:
> >> Hello,
> >>
> >> there is something wrong with your patch
[adding Jonas to cc]
On Fri, 21 Jun 2019 08:36:15 +0200 Xavier wrote:
> Le 21/06/2019 à 06:04, Pirate Praveen a écrit :
> >
> >
> > On 2019, ജൂൺ 20 5:08:24 PM IST, Xavier wrote:
> >> Hello,
> >>
> >> there is something wrong with your patch
Hi team,
I'm planning to file a removal request for node-jquery-textcomplete
soon. It is no longer maintained upstream. It has no reverse (build)
dependency. If anyone is interested to maintain it, please reply.
Thanks
Praveen
--
Pkg-javascript-devel mailing list
Control: tag -1 -help
On Wed, 26 Jun, 2019 at 12:31 PM, Pirate Praveen
wrote:
I need to install ES modules of node-lodash for umd generation
(dagre-d3-renderer is importing from lodash).
After building node-lodash-es from node-lodash, I hit a dead end with
node-graphlibrary as it did
On 2019, ജൂൺ 25 5:08:43 PM IST, Pirate Praveen wrote:
>
>
>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 down
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
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
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
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).
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: 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
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
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 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: 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 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 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
Package: node-terser
version: 3.14.1-2
severity: grave
Control: tags -1 patch
pravi@andhaka:~/forge/debian/git/js-team/vue.js$ sudo apt install
node-terser
[sudo] password for pravi:
Sorry, try again.
[sudo] password for pravi:
Reading package lists... Done
Building dependency tree
Reading
package: libjs-vue
version: 2.5.17+dfsg-1
severity: wishlist
Control: block 930404 by -1
gitlab 11.10.5 needs vue.js 2.6.10
While trying to update, the build failed.
webpack --config debian/webpack.cjs.config.js
Hash: 72f9c82be3887f68bebc
Version: webpack 3.5.6
Time: 283ms
Asset Size
Control: tag -1 help
On Sun, 16 Jun, 2019 at 1:25 PM, Pirate Praveen
wrote:
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
webpack
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
701 - 800 of 992 matches
Mail list logo
