Re: debugging mockup grunt

maybe this is a path to an answer:

http://stackoverflow.com/questions/17718700/cannot-set-breakpoint-inside-function-when-using-require-inside-closure

this guy had also problems debugging, and it seems that it was related
to module level closures.

investigating later...

On Thu, 2014-09-04 at 14:46 -0500, Nathan Van Gheem wrote:
> Johannes,
> 
> 
> I don't have a good answer for you. It's been quite a pain for me in
> the past before also.
> 
> 
> Perhaps this could be a stackoverflow type question? We're more or
> less consumers of the nodejs/grunt/etc toolset and I don't think we
> have a lot of experts here.
> 
> 
> 
> 
> -Nathan
> 
> 
> On Tue, Sep 2, 2014 at 4:44 PM, Johannes Raggam <[email protected]>
> wrote:
>         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
>         
> 
> 
> 
> 
> -- 
> Nathan Van Gheem
> Solutions Architect
> Wildcard Corp

-- 
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

------------------------------------------------------------------------------
Want excitement?
Manually upgrade your production database.
When you want reliability, choose Perforce.
Perforce version control. Predictably reliable.
http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.clktrk

_______________________________________________
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

iEYEABECAAYFAlQPYqcACgkQW4mNMQxDgAf6PgCeIVngpevE0dcX9cT+nBshqtaJ
yeUAoLIoIu39NWvdJFnKjRK8u5rC09mm
=9TdQ
-----END PGP SIGNATURE-----