turndown

On the other hand, their actual dependency list looks closer to this, and this is definitely not comprehensive: https://github.com/ionic-team/capacitor https://github.com/Microsoft/tslib https://github.com/codemirror https://github.com/codemirror/autocomplete https://github.com/codemirror/language https://github.com/marijnh/style-mod https://github.com/marijnh/crelt https://github.com/marijnh/find-cluster-break https://github.com/marijnh/w3c-keyname https://github.com/cure53/DOMPurify https://github.com/electron/electron https://github.com/electron/get https://github.com/debug-js/debug https://github.com/vercel/ms https://github.com/sindresorhus/env-paths https://github.com/sindresorhus/got https://github.com/sindresorhus/is https://github.com/visionmedia/node-progress https://github.com/npm/node-semver https://github.com/malept/sumchecke

This uses the [Turndown JavaScript library](https://github.com/mixmark-io/turndown).

It doesn't. For that you would need to execute a full headless browser first, extract the HTML (document.body.innerHTML after the page has finished loading can work) and process the result. If you're already running a headless browser you may as well run the conversion in JavaScript though - I use this recipe pretty often with my shot-scraper tool: https://shot-scraper.datasette.io/en/stable/javascript.html#... - adding https://github.com/mixmark-io/turndown to the mix will get you Markdown conversion as well.

Turndown works quite well too: https://github.com/mixmark-io/turndown

D'oh, thanks — I use Pandoc plenty to MD -> HTML I totally spaced it can do the inverse. I was briefly looking at [Turndown](https://github.com/mixmark-io/turndown) for projects in the JS ecosystem.

For personal use, and on the topic of Obsidian, I rolled my own form of this... Its quick and dirty, but generally works for my usecase. I tend to push a page through turndown [0] to generate the markdown, then write this into obsidian (also storing things link a copy of the rendered page, link to the source, etc). [0] https://github.com/mixmark-io/turndown

I maintain something similar today, and I'm guessing that the OP uses some combination of the following libraries too (?): - Readability (https://github.com/mozilla/readability) to strip down the page's HTML to a bare minimum. - Turndown.js (https://github.com/mixmark-io/turndown) to convert the plain HTML to a markdown format with the GFM plugins enabled. - Puppeteer (https://github.com/puppeteer/puppeteer) to download the page. It costs me only several cents to parse an entire page, and I think OP can make some money out of this if they get the pricing right. Also, some unsolicited feedbacks on the API: - An option to enable/disable javascript would be great, since not all pages actually need to have it enabled to be parsable. - You can probably tweak the header of the headless browser to bypass the paywalls of some sites. Some are as s

http://markitdown.medusis.com/xsl/html2mk.xsl It looks like 234 lines of code to me. >This attempt for example https://github.com/domchristie/to-markdown/blob/master/src/t.... Is badly written, but still written in a better language. They're using regexps to parse HTML (omfg!), but that kind of nastiness doesn't excuse XSLT as a language. >There is no better templating language than XSLT Except mako, jinja2, django templating language, liquid, etc.

Rather than singing the praise of XSLT (which I love) I'll show an example: this tool transforms any rich text to markdown: http://markitdown.medusis.com It's about 30 lines of XSLT that run in the browser. [Edit: it's not 30 lines but 230, but I was thinking of the number of "rules" (templates) of which there are only 29.] There are very few other tools of its kind and I don't think there exists any client-side, with the same simplicity. This attempt for example https://github.com/domchristie/to-markdown/blob/master/src/t... is about 180 lines of JS, is incomplete, doesn't work with many special cases, etc. There is no better templating language than XSLT; every other templating approach (in PHP or Python on the server, in JavaScript on the client) feels like a horrible kludge once you've experienced XSLT. Yes, XSLT is practically dead,