Use fetch to get images instead of axios (BL-14629)

package.json

@@ -26,7 +26,6 @@
   "//note: ts-node": "really is a runtime dependency",
   "dependencies": {
     "@notionhq/client": "2.2.3",
-    "axios": "^1.6.8",
     "chalk": "^4.1.2",
     "commander": "^9.2.0",
     "cosmiconfig": "^8.0.0",

src/images.ts

@@ -1,6 +1,5 @@
 import * as fs from "fs-extra";
 import FileType, { FileTypeResult } from "file-type";
-import axios from "axios";
 import { makeImagePersistencePlan } from "./MakeImagePersistencePlan";
 import { warning, logDebug, verbose, info } from "./log";
 import { ListBlockChildrenResponseResult } from "notion-to-md/build/types";
@@ -150,10 +149,15 @@ async function processImageBlock(
 async function readPrimaryImage(imageSet: ImageSet) {
   // In Mar 2024, we started having a problem getting a particular gif from imgur using
   // node-fetch. Switching to axios resolved it. I don't know why.
-  const response = await axios.get(imageSet.primaryUrl, {
-    responseType: "arraybuffer",
-  });
-  imageSet.primaryBuffer = Buffer.from(response.data, "utf-8");
+  // Then, in Apr 2025, we started getting 429 responses from imgur through axios,
+  // so we switched to node's built-in fetch (different than the node-fetch package).
+  // Just a guess, but probably imgur keeps locking down what it suspects as code running
+  // to scrape images.
+  // Apparently, imgur is getting to be more and more of a liability,
+  // so we should probably stop using it.
+  const response = await fetch(imageSet.primaryUrl);
+  const arrayBuffer = await response.arrayBuffer();
+  imageSet.primaryBuffer = Buffer.from(arrayBuffer);
   imageSet.fileType = await FileType.fromBuffer(imageSet.primaryBuffer);
 }