Custom template modules

[stefanwalther]

Do you have an example for verb --set includes="my-include-templates" ...?

Tried it both, with a local module and a path following the example of readme-includes, but didn't succeed, always get:

async-helper-base: {%= include("extension-install") %} error: %j TypeError: Cannot read property 'render' of null

But settings in the app seems to be correct:

 store:
   { name: 'verb',
     path: 'C:\\Users\\me\\data-store\\verb.json',
     data: { includes: 'my-readme-includes' } } }

[stefanwalther]

Hi,

I assume the right place to fix this would be .\lib\transforms\init\load.js, right?
I don't see any code there which would load the setting from the data-store ...

Am I missing something?

Regards
Stefan

[tunnckoCore]

@stefanwalther it would it with this.get, imo.

[stefanwalther]

@tunnckoCore, thx, will give it a try ...

[jonschlinkert]

sorry for taking so long on this. @doowb and I have virtually refactored the entire ecosystem underlying verb and other related projects. I'm just migrating now, so any day...

[stefanwalther]

@jonschlinkert Any news on this?

[stefanwalther]

Ping ;-)

[stefanwalther]

Hi, getting this to work would be soooooooo great ;-)
@jonschlinkert & @doowb , any ideas?

[tunnckoCore]

@stefanwalther soon :) If you not noticed they work on underlying tons of packages (see dev branch).
You should definitely try the dev branch + verb-readme-generator.

For that I opened #87 and verbose/verb-generate-readme#2, currently there are resolving problems.

[jonschlinkert]

yes we're very close. fwiw everything is working perfectly locally for me, but we need to add support for npm custom prefixes before we release - I think that's what is breaking @tunnckoCore's build, and probably will cause issues for others.

but I have to say, @doowb and I are really amazed at how awesome this is, and how well everything is coming together as we had planned. We're very close to getting everything "done"! thx for hanging in there and staying interested!

[tunnckoCore]

I think that's what is breaking

hm, that remind me that i didn't try after I fixed the prefix problem. :D I'll try now.

[jonschlinkert]

after I fixed the prefix problem.

what did you do to solve it btw?

[jonschlinkert]

the solutions you pointed to seem like overkill for this, but maybe I'm missing something

[tunnckoCore]

what did you do to solve it btw?

just moved node executable to /usr/local/bin, lol

seem like overkill for this

why? ;d it didn't break anything, which was surprising for me too.

[jonschlinkert]

@stefanwalther have you tried using 0.9? this was implemented

edit: to clarify, loading templates from config was implemented. I don't remember if the CLI flag was hooked up though.

[stefanwalther]

Installing 0.9 (the dev branch), gives me the following errors:

npm install verbose/verb#dev

// Run verb
verb

{ [Error: base-runner#runner Cannot find module 'minimist'] code: 'MODULE_NOT_FOUND' }

After installing minimist, I get some other missing dependencies ... (omit-empty, etc.)

[jonschlinkert]

@doowb and I aren't able to reproduce. Since you installed locally, it's possible that verb is trying to use outdated modules (since npm doesn't force everything to reinstall the way it used to).

did you uninstall everything (delete node_modules and do cache clean) and reinstall? globally and locally?

edit: forgot to mention, you need to install verb globally to use the CLI. I'll fix the readme on the dev branch. also see: https://github.com/node-base/base-runner/blob/master/package.json#L51