--config option does not accept relative path about md-to-pdf

[Zivaga]

:) Sure. I will use it in a more scripted way very soon. If I think about ant improvement, I'll let you know.

Thanks!

[simonhaenisch]

The related code is here:

md-to-pdf/index.js

Lines 83 to 90 in b83e9f1

	// merge config from config file
	if (args['--config-file']) {
	try {
	config = { ...config, ...require(path.resolve(args['--config-file'])) };
	} catch (error) {
	console.warn(chalk.red(`Warning: couldn't read config file: ${args['--config-file']}`));
	}
	}

I don't have access to a Windows machine right now, I'll look into it when I get access to one. Anyway, I'm not sure why path.resolve() would not work here... it's just supposed to take the relative path and make it absolute, relative to the current working directory.

Can you try running this in your directory and see if it works (i. e. prints your config), please:

node -e "console.log(require(path.resolve('generate-pdf\config.json')))"

Update: I just released 2.3.1 which allows to log any errors that occur while trying to read the config file, if you pass the --debug argument. Can you please download the latest version and let me know what error it logs when running

md2pdf --debug --config-file generate-pdf\config.json doc1\doc1.md

The issue is not necessarily related to not being able to find/read the file, but e. g. could also be due to a syntax error within the file (maybe a trailing comma?).

[Zivaga]

Shame on me... I mistyped the folder (generate-pdf instead of generate_pdf .... dash/underscore issue).

In fact, it works like a charm!

I'm really sorry for the not-real-issue.... (the issue where between the chair and the keyboard...) :-/

[simonhaenisch]

No worries, glad you could figure it out 🤓 I haven't thoroughly tested all the different options myself and only on macOS, so I'm thankful for any feedback on potential issues. Gives me a chance to improve the code 😉

[nekloth]

Hi

The relative path changed... it used to consider the relative path from the execution path, now, it considers relative path from the MD file.

It used to work with:

  "stylesheet": [
    ".\\mystyle.css"
  ],

when executed from c:\RepoFolderRoot\

Error is:

 md2pdf --config-file .\generate_pdf\config.json ./doc1/doc1.md
  × generating PDF from ./doc1/doc1.md
    → ENOENT: no such file or directory, open 'c:\RepoFolderRoot\doc1\mystyle.css'

and now works with...

  "stylesheet": [
    "C:\\RepoFolderRoot\\generate_pdf\\mystyle.css"
  ],

It is not very convenient for me, as my stylesheet lifecyle is different from doc lifecycle, and I'm not the only one to use this repo (and of course, all of us do not have the same folder organisation....)