jnordberg/wintersmith — pull request #27 by smebberson (2012-07-03 12:58:19+00:00)
Title: Required change for local development using npm link?

I'm not sure if this is actually required?

I've just sent through another pull request with a feature update. However, in order to do that, I need to setup wintersmith locally so that I could develop against it.

So I forked the code base, clone my forked version of the repository locally, removed wintersmith using npm at the global level, and then used ```npm link``` to link my version of the repository. This allowed me to run ```wintersmith preview``` commands, etc and have it reference my updated code.

However, when I first attempted that, I received the error:

```
smebberson$ wintersmith preview

node.js:201
throw e; // process.nextTick error, or 'error' event on first tick
^
Error: Cannot find module '../lib/cli/'
at Function._resolveFilename (module.js:332:11)
at Function._load (module.js:279:25)
at Module.require (module.js:354:17)
at require (module.js:370:17)
at Object. (/Users/smebberson/Sites/wintersmith.git/bin/wintersmith:3:1)
at Module._compile (module.js:441:26)
at Object..js (module.js:459:10)
at Module.load (module.js:348:31)
at Function._load (module.js:308:12)
at Array.0 (module.js:479:10)
```

The update in the pull request fixed this... I'm not sure how you develop wintersmith locally and if there is a better way I should be doing this?