refactor to use npm instead of custom caching

[svnlto]

Please test this throughly and report back any errors.

@janl @boennemann @caolan @gr2m

[boennemann]

@svnlto Haven't had the time to test this yet, but I wanted to ask what the status of using subfolders in templates is, because the release process setup for my-first-hoodie kind of depends on this.

[svnlto]

@boennemann could you maybe explain what you mean by that? The way templates get handled in this branch, is that we do a npm install and then move the folder out into a folder with the provided name.

[boennemann]

@svnlto I mean rather than copying the template from the my-first-hoodie repository's root folder use a subfolder like template/.

[svnlto]

Why? Oh you mean, have a different structure inside my-first-hoodie altogether?

[boennemann]

Will describe this in another issue. Let's get back to this PR.

[gr2m]

@svnlto just to make sure I'm doing it correctly, can you explain how to link the npm branch to my local hoodie cli command?

[svnlto]

@gr2m you need to use the npm link command for that. Switch to the npm branch, run npm link, then you'll have the hoodie-cli command globally available.

[boennemann]

Haven't tested this locally, but the integration tests now run against those changes which means everything seems to be fine.

[gr2m]

I see a lot of Reading config from /private/tmp/funky/data/config.json. in the terminal (looks like a debug console.log?)
https://gist.github.com/c7ac01f14ec6013db101

Also the output of hoodie start is the same as hoodie start -v

Besides that, looks all good 👍

[svnlto]

I see a lot of Reading config from /private/tmp/funky/data/config.json. in the terminal (looks like a debug console.log?)
https://gist.github.com/c7ac01f14ec6013db101

that's to do with a PR on hoodie-server I'll fix that soon.

Also the output of hoodie start is the same as hoodie start -v

The start command, doesn't have a -v option. You want to use that with the new command.