The current behaviour of the BrowserFetcher class tends to leave instances of the headless chromium browser in a .localchromium folder relative to the directory the application is called from.
This PR updates the BrowserFetcher to take a BrowserFetcherOptions that specifies a directory in the user's local temp folder.
I've also updated the Help text on the chromePath option to remove the statement about only used if the Mermaid switch is enabled as this is not true.
MaxMelcher
commented
1 year ago
The current behaviour of the
BrowserFetcherclass tends to leave instances of the headless chromium browser in a.localchromiumfolder relative to the directory the application is called from.This PR updates the
BrowserFetcherto take aBrowserFetcherOptionsthat specifies a directory in the user's local temp folder.I've also updated the Help text on the
chromePathoption to remove the statement about only used if the Mermaid switch is enabled as this is not true.Fixes #121