Il 16/01/2018 07:24, Pirate Praveen ha scritto:
> Control: tag -1 help
> 
> code is pushed to https://salsa.debian.org/js-team/node-svgo
> 
> some dependencies are still in NEW which I have added to
> https://people.debian.org/~praveen/babel/
> 
> 287 passing (1s)
>   15 failing

I am not sure if I have time to look at this today, but I'd like to mention that
for JS errors like these sometimes it's very useful to use the Chromium 
debugger.

See:
https://nodejs.org/en/docs/inspector/

Procedure tested on sid target and buster client:

1. start your nodejs app on the target with --inspect-brk, for example:
nodejs --inspect-brk /usr/lib/nodejs/mocha/bin/mocha -u tdd

it will print something like:
Debugger listening on ws://127.0.0.1:9229/c0da40fe-d906-4cfa-9bba-a38db47a37b8

then stop at the first JS line

2. open Chromium on the client and go to chrome://inspect
   click on "Open dedicated DevTools for Node" 
   and add the hostname:9229 to the list

It should connect automagically even if the client can be on a different 
machine,
unless you have picky firewalls inbetween ...

Paolo

-- 
Pkg-javascript-devel mailing list
Pkg-javascript-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-javascript-devel

Reply via email to