debugging mockup grunt

i got the idea to rip out the copy and sed section definitions from
mockup-core's MockupGrunt prototype and move it over to the pattern's in
mockup for better encapsulation and separation of concerns.
MockupGrunt's copy and sed sections should then use the config from the
bundle's pattern dependencies.

but before i went ahead, i wanted to set up a debugging environment -
otherwise i would just blindly develop in a trail and error style.

still, i'm failing with debugging.

i tried roughly this:

$ npm install -g node-inspector
$ node-inspector
$ node --debug-brk $(which grunt) bundle-widgets
$ chrome http://0.0.0.0:8080/debug?port=5858

i also tried these grunt tasks according to their documentation:
grunt-debug,
grunt-debug-task

all without luck. chrome is absolutly unresponsive and seems to take
minutes for loading javascript resources, which even do not belong to
mockup.

how are other folks debugging the grunt framework in mockup?


cheers, johannes




-- 
programmatic  web development
di(fh) johannes raggam / thet
python plone zope development
plone framework  team  member
mail: office-//[email protected]
web:  http://programmatic.pro
      http://bluedynamics.com

------------------------------------------------------------------------------
Slashdot TV.  
Video for Nerds.  Stuff that matters.
http://tv.slashdot.org/

_______________________________________________
Plone-developers mailing list
Plone-developers-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
https://lists.sourceforge.net/lists/listinfo/plone-developers

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iEYEABECAAYFAlQGOjAACgkQW4mNMQxDgAfZHQCdE3p+0jWdaQjGKau/pHO9IaIp
GAEAn2NQ6K1tYIqShiLlv/YyzlMuFa53
=a+WA
-----END PGP SIGNATURE-----