Skip to content
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

Gitbook PDF task fails: path undefined #32

Open
fusion809 opened this issue May 1, 2016 · 4 comments
Open

Gitbook PDF task fails: path undefined #32

fusion809 opened this issue May 1, 2016 · 4 comments

Comments

@fusion809
Copy link

Hi,

I cloned this repo installed gitbook-cli via running sudo npm install -g gitbook-cli and ran make from the top-level directory of this repository and I received the error message:

gitbook pdf
(node:17051) fs: re-evaluating native module sources is not supported. If you are using the graceful-fs module, please update it to a more recent version.
(node:17051) fs: re-evaluating native module sources is not supported. If you are using the graceful-fs module, please update it to a more recent version.
info: loading book configuration....OK 
info: load plugin gitbook-plugin-highlight ....OK 
info: load plugin gitbook-plugin-search ....OK 
info: load plugin gitbook-plugin-sharing ....OK 
info: load plugin gitbook-plugin-fontsettings ....OK 
info: >> 4 plugins loaded 

TypeError: Path must be a string. Received undefined
Makefile:16: recipe for target 'book.pdf' failed
make: *** [book.pdf] Error 1

is relevant my operating system is 64-bit Arch Linux, my version of NPM is 3.8.8 and Node.js is 6.0.0.

Thanks for your time,
Brenton

@dothebart
Copy link

I'm seeing this too on debian jessie amd_64.
node --version
v6.3.0
gitbook --version
CLI version: 2.3.0
GitBook version: 2.6.7

@chrisvoncsefalvay
Copy link
Owner

Hi,

I am afraid I did not commit (in all senses of the world) the Gitbookification, so I am a little at a loss as to why this is happening. I am going to dive into this at some point, but if any of you have an idea of what this is, please feel free to hit it!

@dothebart
Copy link

Hi, in my case it was that with earlier versions the commandline simply would work with gitbook pdf. With later versions that changed - so I had to adjust my shellscript:

gitbook pdf./ ./../../books/${BOOK}.pdf

so it contains a source directory, and an output file.
I guess its primarily the error message whats so confusing and not pinpointing the original error.

@brakmic
Copy link

brakmic commented Dec 9, 2016

I had the same problem. A simple gitbook update was the proper remedy.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants