I think it would be way better to explain in the repository: - how do you handle images? - does it handle embedded videos? - does it handle JS? to what extent? - does it handle lazily loaded assets (i.e. images that load only when you scroll down, or JS that loads 3 seconds later after the page is loaded) In general, how does this work? The current readme doesn't do a decent job explaining what the tool exactly is. F…
It can’t handle JS completely because we can’t predict a programs behaviour using static analysis. See Halting Problem for example.
This tool was able to capture three.js applications and other interactive sites quite well.