|
|
%!s(int64=4) %!d(string=hai) anos | |
|---|---|---|
| .. | ||
| lib | %!s(int64=5) %!d(string=hai) anos | |
| linux | %!s(int64=4) %!d(string=hai) anos | |
| mac | %!s(int64=4) %!d(string=hai) anos | |
| win | %!s(int64=4) %!d(string=hai) anos | |
| README.MD | %!s(int64=4) %!d(string=hai) anos | |
| options.json | %!s(int64=5) %!d(string=hai) anos | |
| singlefile_companion.js | %!s(int64=4) %!d(string=hai) anos | |
SingleFile Companion is a program that runs outside the browser. It can:
It uses the Native Messaging API to communicate with SingleFile.
Install SingleFile CLI with NPM
In the companion folder of SingleFile, go into the subfolder corresponding to your OS and your browser. For example, if you use Chome on Linux:
cd companion
cd linux
cd chrome
install.sh executable (Linux/Unix/BSD etc.).chmod +x install.sh
install./install.sh (Linux/Unix/BSD etc.)
install.bat (Windows)
Destination > save with SingleFile Companion or Auto-save > save the page with SingleFile Companion in SingleFileThe options.json file allows configuring SingleFile Companion. Here are the entries you can edit:
savePath: path where to save files (default: SingleFile/companion path)
These options are also available when the option Auto-save > save the page with SingleFile Companion is enabled:backEnd: backend used to save the page (default: "puppeteer")errorFile: path of the file where errors are stored (default: undefined)browserHeadless: whether the browser is launched in headless mode (default: true)browserDebug: whether the browser is launched with the developer tools opened (default: false)