Closed balupton closed 9 years ago
Roger that.
On Thu, Mar 5, 2015, 1:44 AM Benjamin Lupton notifications@github.com wrote:
Hey @docpad/extras-team
I need your help in keeping plugin dependencies up to date.
First we will need to setup a development copy of DocPad:
cd ~ git clone https://github.com/docpad/docpad.git cd docpad cake compile npm link
Then we can setup the extras project:
cd ~ git clone https://github.com/docpad/extras.git docpad-extras cd docpad-extras npm install npm link docpad ./app clone
Then we can find out which plugin deps are out of date by running:
./app outdated
— Reply to this email directly or view it on GitHub https://github.com/bevry/meta/issues/27.
I'll take any that need taskgroup updated.
We could also automate this process if we find or make the right tools :)
Good idea, but for now it needs to get done.
getting this:
(precise)mikeumus@localhost:~/Downloads/Bevry/DocPad/Dev/docpad$ cake compile
events.js:85
throw er; // Unhandled 'error' event
^
Error: spawn /home/mikeumus/Downloads/Bevry/DocPad/Dev/docpad/node_modules/.bin/coffee ENOENT
at exports._errnoException (util.js:746:11)
at Process.ChildProcess._handle.onexit (child_process.js:1046:32)
at child_process.js:1137:20
at process._tickCallback (node.js:355:11)
at Function.Module.runMain (module.js:503:11)
at startup (node.js:129:16)
at node.js:814:3
:blush:
Hey @docpad/extras-team
I need your help in keeping plugin dependencies up to date.
First we will need to setup a development copy of DocPad:
Then we can setup the extras project:
Then we can find out which plugin deps are out of date by running:
It will then produce output like:
Which can be acted upon. Ideally we will have people familiar with the particular plugin they are updating - as that way they can further ensure that the updated dependency won't break anything.