CRX id
koalogomkahjlabefiglodpnhhkokekg
koalogomkahjlabefiglodpnhhkokekg
Description from extension meta
Get a monolith (single static HTML file) of the web page
Description from store
'Monolith of Web' is a Chrome extension ported from CLI tool [Monolith][1]. Monolith is a CLI tool to
download a web page as static single HTML file. 'Monolith of Web' provides the same functionality as
a browser extension by compiling Monolith (written in Rust) into WebAssembly.
## Usage
1. Go to a web page you want to store
2. Click 'Monolith of Web' icon in a browser bar (above popup window will open)
3. Click 'Get Monolith' button
4. Wait for the process completing
5. The generated single static HTML file is stored in your downloads folder
By toggling icons at bottom of the popup window, you can determine to or not to include followings
in the generated HTML file.
- JavaScript
- CSS
- `<iframe/>`
- Images
The button at right-bottom toggles if allow CORS request or not. Please read following 'Permissions'
section and 'CORS Requests in Background Page' section for more details.
## Permissions
- **Required permissions**
- `activeTab`: This extension gets an HTML text and a page title from the active tab to generate a monolith
- `storage`: This extension remembers the last state of toggle buttons at bottom in the popup window.
- **Optional permissions**
- `http://*/*` and `https://*/*`: Allow any cross-origin requests in background page. This is runtime
permission so this extension does not require by default. **Only when you see a broken HTML file is
generated due to CORS error in background page, please enable this option.** The reason of these
permissions are explained in next 'CORS Requests in Background Page' section.
## CORS Requests in Background Page
This extension generates a single HTML file in background page of Chrome extension. Since CSP in a
content script is not applied in a background page, some resources in content's HTML cannot be fetched
in background page.
By default, this extension ignores CORS errors in background page. It is usually not a problem since
resources protected by CSP are usually scripts which don't affect main content. But a broken single HTML
page may be generated due to CORS errors.
When you see a broken page due to the CORS error in background page, please enable 'allow CORS requests'
button at right-bottom in the popup window. Permission dialog will appear to require permissions for
sending CORS requests in background page. After accepting it, CORS request error is disabled and all
resources should be fetched with no error.
After generating a single HTML file with the runtime permissions, this extension will remove the permissions
as soon as possible for security.
[0]: https://github.com/rhysd/monolith-of-web
[1]: https://github.com/Y2Z/monolith
[2]: https://www.youtube.com/watch?v=xBIrFlYE1W0
Latest reviews
- (2022-11-04) Tony Montan: Works great on kiwi browser for android!
- (2022-03-31) Yanghoon Kim: Best EVER!!!! This plugin can save very dynamic html page as well (including plotly)!!!
- (2020-03-13) Varun V Prabhu: For local html files, install a local server app like xampp or wampserver and copy the files to the folder from where the files will be served (like htdocs).
- (2020-02-05) Wade Murdock: Trying to save a locally-saved webpage (you know, the .htm file alongside the folder containing all the images and stuff after you "Save page as..." in Chrome). Waiting for 30sec-1min. Didn't do jack. Toggled off the "including images" button in case my 25+MB of images were the holdup. Still nothing. Tried saving this very webpage I'm typing this on right now (a.k.a. NOT a local .htm file). Still nothing. Off to try the command line version. EDIT: CLI version worked but I had to first install "Rust" on my Windows PC. It didn't support non-http/https webpages, so I had to host my local .htm file on a localhost server using these instructions: https://stackoverflow.com/a/48364392/3511695 Phew... Suggestions: 1. CLI version needs local .htm / .html / whatever file support (instead of just http: / https: ) 2. Plugin needs to be fixed (and should also support local files instead of just http: / https: webpages) 3. Plugin needs a progress bar (unless, when working, it's as instantaneous as the CLI version. In that case, a progress bar might not be needed.)