readability-cli VS node2nix

This is the project: https://gitlab.com/gardenappl/readability-cli It converts a normal webpage to a newone but with Firefox's read mode. And it can save the new page to a local file.

I already use orgmode a bit - mostly through org-roam! I have a pretty inefficient set-up where I save a webpages via SingleFileZ, then use readability-cli on it, then convert the readable output to an orgmode file. Definitely not efficient because I need to manually complete each step, but haven't bothered to try to automate it yet.

Sorry, I didn't get the question. @mozilla/readability is not the same as readability-cli, which I once contributed and packaged with node2nix.

How execute you download a webpage for archiving? I would like something that downloads a clean version of a webpage, for offline reading. I would also like the output file to be renamed using the url title. so far i am using curl -OL but i would also like the site to be parsed and made more "readable" am looking into something like readability-cli (https://gitlab.com/gardenappl/readability-cli) Thought i would ask here, to see if anyone already has something similar. tx EDIT: this‏‏‎‏‏‎‏‏‎‏‏‎­is what i ended up with https://www.reddit.com/r/commandline/comments/kao7mu/help_needed_for_script_to_download_webpages_with/

readable does a good job of cleaning/reformating cruft https://gitlab.com/gardenappl/readability-cli

Readable was new to me, and looks quite good, thanks :-) As a PSA is the project URL https://gitlab.com/gardenappl/readability-cli But in practice it's an npm install.

While running readibility-js installed from npm I am getting this error after the desired ouput. Is there any way to remove this Error from the output output?

You may find something like node2nix helpful (https://github.com/svanderburg/node2nix). This converts your package.json into a Nix expression that can then be cached. You're right that it does require some setup and a bit of Nix knowledge but could yield significant benefits and take a good chunk out of that 20 minutes.

Another option might be to use pnpm instead of Yarn and cache your pnpm dependencies. pnpm actually works a bit like Nix in that it creates a pnpm-lock.yaml file with content-based hashes for the full package.json dependency tree. This enables it to quickly determine which parts of the dependency tree it needs to build and which are already available.

I got it from this github issue in the node2nix repo.

As Gerschtli commented, it may be possible to generate a Nix expression for @mozilla/readability using node2nix. Then get its node_modules path like this and set NODE_PATH to the value.

For node programs, you may be able to find the commands as just packages, or look at https://github.com/svanderburg/node2nix for creating the nix equivalent of a node-modules