Re: [Pkg-javascript-devel] grunt-contrib-uglify and grunt-contrib-copy
On ബുധന് 21 ഡിസംബര് 2016 12:49 വൈകു, Paolo Greppi wrote: > Node-grunt-contrib-copy is also ready but awaits for node-file-sync-cmp Uploaded both. signature.asc Description: OpenPGP digital signature -- Pkg-javascript-devel mailing list Pkg-javascript-devel@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-javascript-devel
Re: [Pkg-javascript-devel] grunt-contrib-uglify and grunt-contrib-copy
On ബുധന് 21 ഡിസംബര് 2016 04:09 വൈകു, Paolo Greppi wrote: > Local Npm module "grunt-contrib-copy" not found. Is it installed? > Local Npm module "grunt-contrib-uglify" not found. Is it installed? > Local Npm module "grunt-contrib-concat" not found. Is it installed? > Warning: Task "concat:core" not found. Used --force, continuing. > > Any idea ? See use-global-tasks.patch in node-jquery-textcomplete. I'd like that path (/usr/lib/nodejs) to be searched as a fallback instead of patching every Gruntfile, can you try to improve the patch in grunt? signature.asc Description: OpenPGP digital signature -- Pkg-javascript-devel mailing list Pkg-javascript-devel@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-javascript-devel
Re: [Pkg-javascript-devel] grunt-contrib-uglify and grunt-contrib-copy
On 21/12/2016 08:19, Paolo Greppi wrote: > On 20/12/2016 03:41, Pirate Praveen wrote: >> On ചൊവ്വ 20 ഡിസംബര് 2016 12:15 രാവിലെ, Paolo Greppi wrote: >>> Hi, >>> >>> while packaging node-rx and trying to build it with grunt, I noticed >>> that apart from a number of non-relevant grunt add-ons related to >>> linting (grunt-jscs and grunt-contrib-jshint), testing (grunt-saucelabs, >>> grunt-contrib-connect, grunt-contrib-qunit) and stuff >>> (grunt-contrib-watch) it depends on grunt-contrib-uglify and >>> grunt-contrib-copy >>> >>> From what I can tell, these I'll really need. >> >> grunt-contrib-copy should be easy. grunt-contrib-uglify has many >> dependencies still to be packaged last time I checked. You can just call >> uglifyjs from commandline in debian/rules. See node-jquery-textchange >> for an example. We can package grunt-contrib-uglify in parallel to avoid >> the manual steps. > > I filed ITPs for both. > > For node-grunt-contrib-uglify I found I can patch away maxmin by > providing a down-to-earth one-liner, this gets rid of a few recursive > dependencies. I just sent the RFS. > > Node-grunt-contrib-copy is also ready but awaits for node-file-sync-cmp Now I have provisional node-grunt-contrib-uglify and node-grunt-contrib-copy installed on the test machine, I patched the Gruntfile.js to run only the relevant tasks, but when I issue: quilt push -a grunt --force I got these errors: Local Npm module "grunt-contrib-copy" not found. Is it installed? Local Npm module "grunt-contrib-uglify" not found. Is it installed? Local Npm module "grunt-contrib-concat" not found. Is it installed? Warning: Task "concat:core" not found. Used --force, continuing. Any idea ? Paolo P.S. The repo is here: https://anonscm.debian.org/git/pkg-javascript/node-rx.git -- Pkg-javascript-devel mailing list Pkg-javascript-devel@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-javascript-devel
Re: [Pkg-javascript-devel] grunt-contrib-uglify and grunt-contrib-copy
On 20/12/2016 03:41, Pirate Praveen wrote: > On ചൊവ്വ 20 ഡിസംബര് 2016 12:15 രാവിലെ, Paolo Greppi wrote: >> Hi, >> >> while packaging node-rx and trying to build it with grunt, I noticed >> that apart from a number of non-relevant grunt add-ons related to >> linting (grunt-jscs and grunt-contrib-jshint), testing (grunt-saucelabs, >> grunt-contrib-connect, grunt-contrib-qunit) and stuff >> (grunt-contrib-watch) it depends on grunt-contrib-uglify and >> grunt-contrib-copy >> >> From what I can tell, these I'll really need. > > grunt-contrib-copy should be easy. grunt-contrib-uglify has many > dependencies still to be packaged last time I checked. You can just call > uglifyjs from commandline in debian/rules. See node-jquery-textchange > for an example. We can package grunt-contrib-uglify in parallel to avoid > the manual steps. I filed ITPs for both. For node-grunt-contrib-uglify I found I can patch away maxmin by providing a down-to-earth one-liner, this gets rid of a few recursive dependencies. I just sent the RFS. Node-grunt-contrib-copy is also ready but awaits for node-file-sync-cmp >> Has anybody experience with these ? Should I just package them as ? >> >> The current state of node-rx is here: >> >> https://anonscm.debian.org/git/pkg-javascript/node-rx.git >> -- Pkg-javascript-devel mailing list Pkg-javascript-devel@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-javascript-devel
Re: [Pkg-javascript-devel] grunt-contrib-uglify and grunt-contrib-copy
On ചൊവ്വ 20 ഡിസംബര് 2016 12:15 രാവിലെ, Paolo Greppi wrote: > Hi, > > while packaging node-rx and trying to build it with grunt, I noticed > that apart from a number of non-relevant grunt add-ons related to > linting (grunt-jscs and grunt-contrib-jshint), testing (grunt-saucelabs, > grunt-contrib-connect, grunt-contrib-qunit) and stuff > (grunt-contrib-watch) it depends on grunt-contrib-uglify and > grunt-contrib-copy > > From what I can tell, these I'll really need. grunt-contrib-copy should be easy. grunt-contrib-uglify has many dependencies still to be packaged last time I checked. You can just call uglifyjs from commandline in debian/rules. See node-jquery-textchange for an example. We can package grunt-contrib-uglify in parallel to avoid the manual steps. > Has anybody experience with these ? Should I just package them as ? > > The current state of node-rx is here: > > https://anonscm.debian.org/git/pkg-javascript/node-rx.git > signature.asc Description: OpenPGP digital signature -- Pkg-javascript-devel mailing list Pkg-javascript-devel@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-javascript-devel
[Pkg-javascript-devel] grunt-contrib-uglify and grunt-contrib-copy
Hi, while packaging node-rx and trying to build it with grunt, I noticed that apart from a number of non-relevant grunt add-ons related to linting (grunt-jscs and grunt-contrib-jshint), testing (grunt-saucelabs, grunt-contrib-connect, grunt-contrib-qunit) and stuff (grunt-contrib-watch) it depends on grunt-contrib-uglify and grunt-contrib-copy >From what I can tell, these I'll really need. Has anybody experience with these ? Should I just package them as ? The current state of node-rx is here: https://anonscm.debian.org/git/pkg-javascript/node-rx.git -- Pkg-javascript-devel mailing list Pkg-javascript-devel@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-javascript-devel
