Monolith needs to become an importable crate about monolith HOT 4 OPEN

Aside from being a CLI tool, monolith has potential to be used as a library and published on crates.io. For this feature to be implemented we first need to design API for monolith, for the most part how we provide options (instead of parameters via CLI).

from monolith.

Big shout out and thanks to @jstasiak for releasing the monolith crate name for this project on crates.io!

from monolith.

I see this is now an importable crate, but it seems like much of the functionality is held within main, which can't be imported and used easily. Has anyone had any luck with using this crate as a library?

from monolith.

Yeah.... so, about that... basically, before it could be used as a library, an API of sorts needs to be drafted, and it needs to be done in a way that allows people to build their own archiving tools, consistent with how other CLI crates expose their APIs, and follows good practices. In all honesty, it's really far down the current TODO list since the tool itself needs to get more features, some highly-requested stuff like support for MHT format, blacklisting domains, recursive saving of pages, etc. Slowly but surely it'll get there, ideally I'd really love to see Firefox use it as a way to save monolithic HTML documents without any external tools or services.

from monolith.