From 2ffe63a31dd681476c25c358a3d019a5a1c3842f Mon Sep 17 00:00:00 2001 From: Marek Kotewicz Date: Thu, 9 Jul 2015 08:55:45 +0200 Subject: [PATCH 1/2] readme update - debugging embark --- README.md | 11 +++++++++++ 1 file changed, 11 insertions(+) diff --git a/README.md b/README.md index e550ce35..7c6d99d1 100644 --- a/README.md +++ b/README.md @@ -213,3 +213,14 @@ LiveReload Plugin ====== Embark works quite well with the LiveReload Plugin + +Debugging embark +====== +Becuase embark is internally using grunt tasks, debugging is not straightforward. Example + +- you want to debug `embark deploy` +- normally you would write something like `node-debug -p 7000 embark -- deploy` +- This gives you nothing with embark. If you look at `deploy` command in [`./bin/embark`](https://github.com/iurimatias/embark-framework/blob/develop/bin/embark#L32-L35) you will notice that it internally runs grunt task `grunt deploy_contracts:[env]` +- with this knoledge we can prepare proper command to start debugging +- `node-debug -p 7000 grunt -- deploy_contracts:development` +- [here](https://github.com/iurimatias/embark-framework/blob/develop/tasks/tasks.coffee) is list of all debugable grunt tasks From 37fd6e1e1387c7e2bf892124c79f270143f872e5 Mon Sep 17 00:00:00 2001 From: Marek Kotewicz Date: Thu, 9 Jul 2015 11:03:06 +0200 Subject: [PATCH 2/2] fixed typos --- README.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/README.md b/README.md index 7c6d99d1..b94cb780 100644 --- a/README.md +++ b/README.md @@ -216,11 +216,11 @@ Embark works quite well with the LiveReload Plugin Debugging embark ====== -Becuase embark is internally using grunt tasks, debugging is not straightforward. Example +Because embark is internally using grunt tasks, debugging is not straightforward. Example - you want to debug `embark deploy` - normally you would write something like `node-debug -p 7000 embark -- deploy` - This gives you nothing with embark. If you look at `deploy` command in [`./bin/embark`](https://github.com/iurimatias/embark-framework/blob/develop/bin/embark#L32-L35) you will notice that it internally runs grunt task `grunt deploy_contracts:[env]` -- with this knoledge we can prepare proper command to start debugging +- with this knowledge we can prepare proper command to start debugging - `node-debug -p 7000 grunt -- deploy_contracts:development` -- [here](https://github.com/iurimatias/embark-framework/blob/develop/tasks/tasks.coffee) is list of all debugable grunt tasks +- [here](https://github.com/iurimatias/embark-framework/blob/develop/tasks/tasks.coffee) is list of all debuggable grunt tasks