{"id":1197,"date":"2013-07-20T11:38:33","date_gmt":"2013-07-20T17:38:33","guid":{"rendered":"http:\/\/www.mooreds.com\/wordpress\/?p=1197"},"modified":"2013-07-23T14:53:34","modified_gmt":"2013-07-23T20:53:34","slug":"hooks-and-cordova-cli","status":"publish","type":"post","link":"https:\/\/www.mooreds.com\/wordpress\/archives\/1197","title":{"rendered":"Hooks and Cordova CLI"},"content":{"rendered":"

Hooks are scripts that you can run before and after each stage of the Cordova CLI lifecycle<\/a>. They live in a projecthome\/.cordova\/hooks\/before_xxx<\/code> (or after_xxx) where xxx is the project lifecycle stage (prepare, build, etc).<\/p>\n

They are somewhat documented here<\/a>, and here’s an example<\/a> you can “borrow” from. As we’ll see in the next few posts, they are a lifesaver at dealing with some of the current deficiencies of Cordova CLI.<\/p>\n

But to start with, all you need to know is that hooks are chunks of code that are passed the project base directory as the first argument (and therefore available via var rootdir = process.argv[2];<\/code> for node, or $1<\/code> for shell scripts). These chunks can be any kind of executable code (shell\/node\/perl\/python\/compiled c, etc). All I focus on here are project specific hooks–I don’t know how module hooks would work.<\/p>\n

I have typically used hooks to move and manipulate files and used node (though you can use any scripting language) and am a node newbie–therefore stackoverflow and the node filesystem API docs<\/a> were my friends.<\/p>\n

Each hook is executed in alphabetical order within the before_ or after_ directory. A good idea is to name each hook to make the order explict:<\/p>\n