webmention.io VS node-fetch

Webmentions (webmention.io) are a way to bring social activity and interactivity to your site without having it on your platform itself or needing to have complex systems in place. Harness the activity, audience, and functionality from existing platforms.

async function getMentions(url) { let mentions = []; let page = 0; let perPage = 100; while (true) { const results = await fetch( `https://webmention.io/api/mentions.jf2?target=${url}&per-page=${perPage}&page=${page}` ).then((r) => r.json()); mentions = mentions.concat(results.children); if (results.children.length < perPage) { break; } page++; } return mentions.sort((a, b) => ((a.published || a['wm-received']) < (b.published || b['wm-received']) ? -1 : 1)); }

Webmentions: https://webmention.io/

In the interim, I found myself pondering why every webmentions-on-Hugo solution I’d ever found up to now used JavaScript, rather than trying to do it purely in Hugo. After all, Hugo sports plenty of data-grabbing horsepower. For example: in my own experience to date, I’ve found Hugo's getJSON feature just as useful as the node-fetch on which the aforementioned JS relied to grab data from webmention.io.

One of the building blocks for such a system might be something like:

https://webmention.io/

{ "type": "feed", "name": "Webmentions", "children": [ { "type": "entry", "author": { "type": "card", "name": "Jon Kuperman", "photo": "https://webmention.io/avatar/pbs.twimg.com/a52326c0080bba610767505756be327891f63722c0ceb6515de5840097c65cb9.jpg", "url": "https://twitter.com/jkup" }, "url": "https://twitter.com/jkup/status/1365400108016291841", "published": "2021-02-26T20:35:28+00:00", "wm-received": "2021-02-26T21:23:21Z", "wm-id": 1048723, "wm-source": "https://brid.gy/comment/twitter/raymondcamden/1365399913987792900/1365400108016291841", "wm-target": "https://webmentions.vercel.app/posts/alpha/", "content": { "html": "hello!\n\"u-mention\" href=\"https://twitter.com/raymondcamden\">\n\"u-mention\" href=\"https://webmentions.vercel.app/\">\n\"u-mention\" href=\"https://www.raymondcamden.com/\">", "text": "hello!" }, "in-reply-to": "https://webmentions.vercel.app/posts/alpha/", "wm-property": "in-reply-to", "wm-private": false }, { "type": "entry", "author": { "type": "card", "name": "Jonathan Bossenger", "photo": "https://webmention.io/avatar/pbs.twimg.com/211d2d7837e89b60b4399dfc76f5aa3aad8b2d792335f08ecd65ce6c73da48cb.jpg", "url": "https://twitter.com/jon_bossenger" }, "url": "https://twitter.com/jon_bossenger/status/1365402390212587527", "published": "2021-02-26T20:44:32+00:00", "wm-received": "2021-02-26T21:23:17Z", "wm-id": 1048721, "wm-source": "https://brid.gy/post/twitter/raymondcamden/1365402390212587527", "wm-target": "https://webmentions.vercel.app/posts/alpha/", "content": { "html": "I assume the copy of Edge runs on Ubuntu? \"https://webmentions.vercel.app/posts/alpha/\">webmentions.vercel.app/posts/alpha/\n\"u-mention\" href=\"https://webmentions.vercel.app/\">", "text": "I assume the copy of Edge runs on Ubuntu? webmentions.vercel.app/posts/alpha/" }, "mention-of": "https://webmentions.vercel.app/posts/alpha/", "wm-property": "mention-of", "wm-private": false }, { "type": "entry", "author": { "type": "card", "name": "? cannot even", "photo": "https://webmention.io/avatar/pbs.twimg.com/1f2ab7fe8fb6c20b4a2be803b95f6559677d0b88577a091c2b1755f70dff4247.jpg", "url": "https://twitter.com/diffalot" }, "url": "https://twitter.com/diffalot/status/1365406879459860480", "published": "2021-02-26T21:02:22+00:00", "wm-received": "2021-02-26T21:23:06Z", "wm-id": 1048716, "wm-source": "https://brid.gy/post/twitter/raymondcamden/1365406879459860480", "wm-target": "https://webmentions.vercel.app/posts/alpha/", "content": { "html": "Testing webmentions Alpha Post \"https://webmentions.vercel.app/posts/alpha/\">webmentions.vercel.app/posts/alpha/", "text": "Testing webmentions Alpha Post webmentions.vercel.app/posts/alpha/" }, "mention-of": "https://webmentions.vercel.app/posts/alpha/", "wm-property": "mention-of", "wm-private": false } ] }

node-fetch.

To execute the algorithm, we will use Node.js (for the JavaScript runtime) and node-fetch (for network requests). This means we will run the code locally from the command line. For this project, we will have an output folder to store all the README data, as well as a list (queue) of repository URLs to visit. Before diving into the code, it is important to plan the input and output of the algorithm. For this web crawler, we will start at a valid GitHub repository page, which would be one URL string. After visiting each page with a README, we will export the data into a new file. Now lets cover the process of requesting a repository page from a URL. For this, we only care about saving the README file that is displayed, and we will ignore any other links that GitHub displays (such as the navbar). We will send a URL request with node-fetch, and retrieve the result of a HTML string. If we convert the HTML string to a DOM Tree, we can search for a specific element. GitHub stores the README file under a div with the class "markdown-body". We can use a library called 'jsdom' to use Browser API methods, and return a specific node.

Note: In case you run into install reference error: fetch isn’t defined, ensure you install node-fetch

Node Fetch is a JavaScript library tailored for Node.js that simplifies making HTTP requests. It offers a straightforward and Promise-based approach for fetching resources from the internet or server, such as GET, POST, PUT, and DELETE requests. Designed for server-side applications, it's compatible with the Fetch API, allowing easy code transition between client-side and server-side environments.

Would anyone be interested in an article about the crusade to move JS to ESM? I've been considering writing one, here's a preview:

Sindresorus wrote a gist "Pure ESM modules"[0] and converted all his modules to Pure ESM, breaking anyone `require`ing his code; he later locked the thread to prevent people from complaining. node-fetch released a pure ESM version a year ago that is 16x less popular than the CommonJS version[1]. The results of these changes broke a lot of code and resulted in many hours of developers figuring out how make their projects compatible with Pure ESM modules (or decide to ignore them and use old CommonJS versions)--not to mention the tons of pointless drama on GitHub issues.

Meanwhile, TC-39 member Matteo Collima advocated a moderate approach dependent on where your module will be run [2]. So the crusade is led not by the Church, but by a handful of zealots dedicated to establishing ESM supremacy for unclear reasons (note how Sindresorus' gist lacks any justifications). It's kind of like the Python 2 to 3 move except with even less rationale and not driven by the core devs.

0 - https://gist.github.com/sindresorhus/a39789f98801d908bbc7ff3...

1 - https://www.npmjs.com/package/node-fetch?activeTab=versions

2 - https://github.com/nodejs/node/issues/33954#issuecomment-924...

https://www.npmjs.com/package/node-fetch is pretty standard assuming you're referring to an HTTP client library

The API is CORS-enabled, meaning you’ll have to use the getArticles() functions from your backend. For making the actual request, you can use the fetch() function, available since Node.js v18. For older versions of Node.js, you can use a fetch()-compatible library like node-fetch.

I have the same setup. On node 18 fetch would not go through. I changed 127.0.0.1 to localhost in my config/env. More info here

I am making a bot that is supposed to take data from Upland's database from the account "dcrawtu15ye". I am using autocode to take it and I have found some ways to use it but some of my code still comes back as null. I have been using the eos docs to find info and all it can do right now is get account info if I use console.log(await rpc.get_account('dcrawtu1u5ye'));. I am using the dependency node-fetch. I wanted to know if there is something wrong with the code below. I also used greymass from this list and this article supposedly might help too.

The RSS feed's URL will then need to be requested over the network. The native fetch API of JavaScript will be used since it is the most efficient. It undoubtedly works in browsers, and it appears that Node has a pretty well-liked implementation of it.