xyfir / node-calibre Goto Github PK

After a book has been added to calibre (calibredb command), for further conversion using calibre-convert command, the absolute path to imported book has to be specified.
The default calibre library path should be used/assumed,
how can it be determined from the calibre CLI tools?

Alternatively this wrapper could offer a method/other means for getting the library path –
or automatically converting relative paths to absolute paths inside the library path.

• Methods for each command: calibre.db.*, calibre.ebookConvert, etc
  • calibre.db.add()
    • #8 Among returned data, supply array of duplicate books
• Improve error checking by looking at the command's output and checking for specific values based on the command.
• Return result object that contains the original full output string and also parsed data relevant to the command.
• Each method takes relevant arguments, and not just the general args and options from run().

From camelCase to kebab-case.

This way instead of needing to do

calibre.run('calibredb list', [], { 'for-machine': null });

you could do

calibre.run('calibredb list', [], { forMachine: null });

Example: set_metadata's --field.

By default calibredb add doesn't add books that already exists in calibre library (which is good).
However, in the script it has to be known sometimes (e.g. not further continuing).
It would be nice if the calibredb add callback gets an extra argument for an array of duplicate books.

So instead of needing to do

calibre.run('calibredb list', [], { 'for-machine': null });

you could do

calibre.run('calibredb list', { 'for-machine': null });

In WSL (Bash on Windows) shell, the binaries/commands can't be found by node-calibre (e.g. 'calibredb').

(node:9474) UnhandledPromiseRejectionWarning: Unhandled promise rejection (rejection id: 1): Error: Command failed: calibredb list --library-path ""
/bin/sh: 1: calibredb: not found
(node:9474) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.

Support using child_process.spawn(), and potentially replace child_process.exec() entirely with child_process.spawn().