chrisvoncsefalvay / learn-julia-the-hard-way

Learn Julia the hard way!
https://app.gitbook.com/@chrisvoncsefalvay/s/learn-julia-the-hard-way/
Other
772 stars 153 forks source link

Gitbook PDF task fails: path undefined #32

Open fusion809 opened 8 years ago

fusion809 commented 8 years ago

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 commented 8 years ago

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 commented 8 years ago

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 commented 8 years ago

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 commented 7 years ago

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