Getting the following alert

which dependabot cannot handle

should use a ^ like the other dependancies in the package

   "node-fetch": "^2.6.5", 

There are workarounds, so I am not blocked but it is easier if the package maintainer sets up their package up correctly

Nb: It is okay to pin devDependancies

Describe the bug
Deploying to netlify:

10:20:10 PM: > cross-env ELEVENTY_ENV=production eleventy
10:20:11 PM: [flamedfury.com] Something went wrong with your request to webmention.io! TypeError: Cannot read properties of undefined (reading "length")
10:20:11 PM:     at /opt/build/repo/node_modules/@chrisburnell/eleventy-cache-webmentions/eleventy-cache-webmentions.js:108:28
10:20:11 PM:     at processTicksAndRejections (node:internal/process/task_queues:96:5)
10:20:11 PM:     at async fetchWebmentions (/opt/build/repo/node_modules/@chrisburnell/eleventy-cache-webmentions/eleventy-cache-webmentions.js:104:3)
10:20:11 PM:     at async filteredWebmentions (/opt/build/repo/node_modules/@chrisburnell/eleventy-cache-webmentions/eleventy-cache-webmentions.js:133:23)
10:20:11 PM:     at async filtered (/opt/build/repo/node_modules/@chrisburnell/eleventy-cache-webmentions/eleventy-cache-webmentions.js:238:32)
10:20:11 PM:     at async TemplateDataInitialGlobalData.getData (/opt/build/repo/node_modules/@11ty/eleventy/src/TemplateDataInitialGlobalData.js:24:25)
10:20:11 PM:     at async /opt/build/repo/node_modules/@11ty/eleventy/src/TemplateData.js:337:26
10:20:11 PM: [flamedfury.com] 0 filtered Webmentions pulled from cache.

To Reproduce
Steps to reproduce the behavior:

1. Go to flamedfury/flamedfury.com@6876e3b
2. start deploy to netlify

Environment:

• Eleventy Version: 1.0.2

Additional context
Builds and displays Webmentions locally, has issue when deploying to Netlify!

The documentation has links to Webmention.io with per-page=9001 which seemed like a reasonable limit at the time, but it’s not unreasonable that someone could have more Webmentions than that.

For fresh builds, it may be wise to suggest a higher limit and implement subsequent page fetches (and waits?) based on API response.

Describe the bug

I went through the installation instructions (thank you for that by the way), and it looks like I should be able to set a custom cache directory, but it doesn't get used when I pass it in.

To Reproduce
Steps to reproduce the behavior:

Following your Webmention setup:

Step 1. Create a config file and pass a custom directory:

const { defaults } = require("@chrisburnell/eleventy-cache-webmentions")()

// Load .env variables with dotenv
require("dotenv").config()

module.exports = Object.assign(defaults, {
    domain: "https://EXAMPLE.COM",
    feed: `https://webmention.io/api/mentions.json?domain=EXAMPLE.COM&token=${process.env.WEBMENTION_IO_TOKEN}&per-page=9001`,
    key: "links",
    directory: "_cache",
})

Step 2: Run the build to fetch webmentions.
Step 3: See that webmentions weren't put in your chosen directory.

Expected behavior

The cache file should be in _cache instead of .cache

Environment:

• Ubuntu 22.02
• Eleventy Version: V2 Beta (currently, but I've had this issue for a while now)

Additional context

To get around this issue, I'm currently using patch-package to apply a fix postinstall that passes options.directory into the AssetCache. I pasted my patch file below.

-	let asset = new AssetCache(options.uniqueKey)
+	let asset = new AssetCache(options.uniqueKey, options.directory)
 	asset.ensureDir()
 
 	let webmentions = []

I'm not sure if it's really that one line that is the solution, but it seems to fix it for me.