No TOC generated #91
Comments
|
please see the dev branch, and #78. 200+ commits ahead of master. sorry for the issues, I'm working to get them fixed with the refactor |
|
@phun-ky in short @jonschlinkert , maybe should add quick notice in master branch. :) Cheers, |
yeah that's good advice. I'll do that thx |
|
@tunnckoCore in short, no, still not producing any toc with the same approach |
|
Are you sure you are using the dev branch? I'm with latest dev commit (okey, not so latest - 4 commits behind it) and it works. Please check I'm with that and works as expected. |
|
try adding this to package.json: {
"verb": {
"toc": true
}
} |
|
@jonschlinkert tried that, not helping. but I see now that my global installed verb is: Will try to force the reinstall of verb |
|
Nope: None of this works.. |
Seems like you didn't install |
|
that is the old version of verb though. dev is 0.9.0. To install dev you need to do |
|
@tunnckoCore tried this several times, it will not install globally: But I noticed that I have two global node_modules :S
The latter got |
What system you are using? I'm on ArchLinux and I was using nodejs and npm directly installed, not
Yea, the whole problem, in short, is that So currently the fix is to use some version manager - I didn't use |
|
Using: Using |
|
@phun-ky thanks so much for working through this. that's awesome of you. as soon as we can @doowb and I will review your code in more detail to see if we can figure out what's happening. early feedback like this is so helpful for creating an awesome project and ecosystem. verb is pretty awesome, and hopefully you'll get a chance to see that. thanks |
I'm helping :)
Yep, that's the problem, it uses
And one more question: how you installed not through npm, then install wanted nodejs version. |
you are indeed! thank you! |
|
@tunnckoCore removed every trace of node, installed n via curl, Shouldn't these point to some Tried to install with this prefix aswell: But I get this: I am out of clues now :S |
|
Update: I now have:
My My My And the produced This is how I run it (and I get an error) |
|
Seriously, I don't know, it's strange. The only I can say is "too much done" and I think this error is different thing. Verbfile not needed, verb-toc globally not needed (it is included in verb-readme-generator), flag when running is not need, because in config is true. |
|
Removed |
|
That error indicates that Maybe we can step back for a moment and start from the beginning. The following is all that should be needed (before you run this, for debugging purposes if there is still a $ npm i -g verbose/verb#dev verb-readme-generator && verb readmeThere should not be any additional effort or derpfiles required. If that doesn't work, there's a bug. I'd like to just focused on getting that specific thing fixed. |
|
Same result. And here is the |
Hmm, are you using a custom npm prefix? (I scanned the above comments where @tunnckoCore mentioned this, but didn't see a direct answer to that. Only that you're using edit: this looks like a bug either way. if you're using a custom prefix I think I know how to resolve it. If not, I have an idea of what it might be. |
|
@jonschlinkert it's obvious that he use custom prefix, I created some screencast. |
I don't think it's obvious. I don't use looking at the screencast edit: nvm I think I misread what you said about home/defaul |
|
what did you use to create the screencast? |
Just the asciinema archlinux package :) they also have packages for other distros, but I don't know if there's for Mac. edit: actually, yes https://asciinema.org/docs/installation, it's awesome! |
|
@tunnckoCore watching it now, but can you try without the scaffolding? just in case.. |
|
@tunnckoCore here is my screencast, same result: |
|
I'm watching it now.
it doesn't do anything special - just copy files and my .verb.md layout. |
|
@phun-ky you miss to add And can you then try with |
|
@tunnckoCore https://asciinema.org/a/54h7rg221fpttjux2p4efu1bo
package.json: |
|
@tunnckoCore the error in the screencast: |
|
@tunnckoCore after realizing that @jonschlinkert still no |
Absolutely no, that's the coolness of
The cool thing of asciinema is that you can directly copy paste from the cast :) @jonschlinkert damn, that's strange, lol!! 😆 isn't it? 🚀 I give up. lol |
|
SIGH Made it work.. But to get this to work, these criteria has to be met:
I think some of the attributes has to be set to use the default layout, but you have to set a layout it seems to produce the TOC.. |
No. Remove it, and install it globally, but add
Make sense. The last error
Yes. The minimum is to set edit:
needed if you want to run just |
executing: But sadly, now I get that |
|
@tunnckoCore Hm, If i run: I get that error, regardless now if I have The globally installed And locally: Success.. |
|
And the |
|
@tunnckoCore @jonschlinkert and just to be clear, the doc for |
yea, verb look on both places and can load from both places, but better is to be instaleld globally, it not make sense to install it for every project - cost at least dev time.
It's another issue (it's easy), that I also have, but didn't opened issue - I'll open now or I'll PR directly there. So, finally, locally works? If that works, maybe Jon more clear idea now what and why is happening. edit: Opened base/base-runner#5 for |
well, we're making progress lol. that's a bug related to adding config defaults. like @tunnckoCore says that should be easy to fix. In the meantime, try running |
remember we're still on some of these things sound like they work as expected, some do not:
|
|
closing since TOC logic has been updated a few times since this issue, and verb uses the verb-toc plugin for this. If you still have issues with toc please open an issue on verb-toc or verb-readme-generator if that's what you're using |
I've installed both
verbandverb-cli, executed it like this:verbOk, it went through my
.verb.mdfile and polished it.And, as the documentation clearly states:
And naively I believed the phrasing you have:
So I will try to explain what I am doing, and what I expect:
Added
<!-- toc -->to the.verb.mdfile, no TOC generatedExecuted
verb --toc, no TOC generatedExecuted
verbwith"verb" : { "toc": true}inpackage.json, no TOC generatedExecuted
verbwith"verb --toc" : { "toc": true}inpackage.json, no TOC generatedAdded a
verbfile.jswith this:Resulting in:
[TypeError: verb.extendWith is not a function]Added a
verbfile.jswith this:Resulting in:
[Error: Invalid taskdefault. Registerdefaultbefore calling run.]So what is the diddly-o here?
Versions:
alexander@alexander-w541-laptop ~/Workspace/proj f-verb ● npm -v && node -v && verb -v
3.3.12
v5.1.0
The text was updated successfully, but these errors were encountered: