The code path to produce human-readable error messages if addFilter() etc are called on a non-function is throwing

[LeaVerou]

(Using 3.0.0.alpha.17)

As part of almost every 11ty config, I have this little snippet:

for (let name in filters) {
	if (typeof filters[name] === "function") {
		config.addFilter(name, filters[name]);
	}
}

Where filters is an import containing multiple util functions.

In the project I’m currently working on, at some point I started getting this error message:

I was puzzled. There was no name anywhere! Clicking through to the call stack revealed this:

Which made me realize what was happening: I had added some export const to my filters file, and trying to add these as filters was understandably throwing.

It looks like there is already a code path to produce a better error message, but that is throwing.
Fixing it would be a reasonable first step. I’d argue that this is not a reason for complete and total failure either — but I’m going to open another issue for that.

[zachleat]

Caught the same in the latest alpha, sorry about that! Fixed here 17a065c#diff-ef495efa0b1aa47730f5ecc48482e10c944d1be2a28f386bd234276a488902d6R309 with #3384

Shipping with 3.0.0-alpha.18