-
Notifications
You must be signed in to change notification settings - Fork 80
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
TOC not generating #169
Comments
Try installing it locally in the project you're trying to build. |
I just tried this, but same results. No TOC with chapters built.
I also tried
They build the page, but the generated TOC has nothing from my |
Mind if I ask what environment you are using? On my end the left side just says "My project" with nothing underneath. |
I'm on OSX. I'm going to mark this as a bug. The issue is probably here https://github.com/docpress/docpress-core/blob/master/lib/tocify.js#L219 |
Possible fix for docpress/docpress#169
Thanks. FYI. I just tried this on Windows 10's Linux Subsystem and this is what I got.
|
@cvax did you try the current PR that resolve the problem? |
@Kikobeats Sorry, just gave it a shot now. This is what I got with that PR in docpress-core.
Without that PR it would build, but no TOC. I tried changing the path, but anything I put in was giving this error. |
Looks like a path issue still exists.. |
@knownasilya ya, looks like there are still some Windows incompatible pathing coded into |
Same issue for me, ToC is not created. Using Windows 10. |
@knownasilya @Kikobeats just wanted to ask if there was any other info you might need to potentially address this. Thanks. |
actually I don't know |
I had issues debugging with |
Sorry mate, never tried it. :(
|
I think I know what's up here. Docpress keeps a list of files like so: /* _docpress.json */
{
sources: {
'README.md': ...
'intro/index.md': ...
}
} These are generated from docpress-core, and it assumes posix-style /slash/delimited/paths. Unfortunately there are many places that assume this :\ |
@rstacruz Running from Win10 Linux Subsystem has the posix paths though. Maybe the issue on that Linux Subsystem is different than the issue on regular Windows. |
anyone get this working on windows yet? |
I have the same issue on MAC OSX 10.11.6, Node v7.1.0 |
On windows I downloaded the sources of the docpress project itself and when I tried to generate the docs I got the same error. |
I used docpress for https://github.com/namedframework/docs and worked fine from Mac few years back. Working documentation is at https://docs.namedframework.com/ I am trying to update same documentation now on Windows system and TOC is not generating. OS: Windows 10 (Version 1909) |
I am not sure what the issue is, but I can't get it to generate the TOC as described in your usage instructions. I setup a super simple test over here: https://github.com/cvax/docpresstest
I am on docpress 0.7.0 and Windows 7.
When I serve this page it generates the root README.md just fine, but it doesn't build any of the TOC's README.md in /docs folder. I also tried to clone one of your showcase's docs to try serving, same result. Root README.md works, but TOCs didn't build.
Is this a docpress installation issue? Perhaps Windows issue? I just installed the npm package globally. There were some npm deprecated warnings on minimatch, native-or-bluebird, and fsevents though.
The text was updated successfully, but these errors were encountered: