Customize Feed Parsing
By default, Feedcanon uses Feedsmith to parse feeds. You can use any feed parser by providing a custom parser that implements the adapter interface.
Interface
The parser option must implement ParserAdapter<T>:
type ParserAdapter<T> = {
parse: (body: string) => MaybePromise<T | undefined>
getSelfUrl: (parsed: T, responseUrl?: string) => string | undefined
getSignature: (parsed: T, responseUrl: string, comparedUrls?: Array<string>) => string
}parse
Parse the feed body and return your feed type, or undefined if parsing fails. Both sync and async parsers are supported:
parse: (body: string) => MaybePromise<Feed | undefined>getSelfUrl
Extract the self URL from the parsed feed. This is typically the atom:link rel="self" or similar declaration:
getSelfUrl: (feed: Feed, responseUrl?: string) => string | undefinedThe responseUrl argument is the URL the feed was fetched from. A relative self URL is resolved against it afterwards, so most parsers can ignore it. The default parser uses it to resolve the self link against the feed's xml:base first (RFC 4287 §2). Called without it, the default parser applies only an absolute xml:base. Feedsmith keeps only the xml:base on the root element, so a base set on the channel or on the link itself is ignored.
A self link in the response's Link header takes precedence. This one is tried only when that one fails validation.
getSignature
Return a string representing the feed's identity. Two feeds are treated as the same when their signatures are equal. Used to compare feeds when exact body matching fails:
getSignature: (feed: Feed, responseUrl: string, comparedUrls?: Array<string>) => stringThe responseUrl argument is the URL the feed was fetched from. The comparedUrls argument holds the URLs of the feeds it is compared with. Feedcanon asks for up to two signatures of each feed. The first call passes no comparedUrls, and the default parser reduces URLs on the feed's own host or on the site's host to their path, so two copies that each link their own host match. When those signatures differ, a second call passes them, and the default parser keeps the host of those URLs and only drops protocol, www and trailing slash, so two copies on different hosts that link the same URLs match, while feeds that link each other's host do not. URLs on any other host stay as written. A custom parser can ignore both.
Build the signature from fields that stay the same between requests:
- Feed title and description
- Item GUIDs or URLs
- Item timestamps
Leave out fields that change with every request or with the URL the feed was fetched from, such as the build date or the self URL.
Examples
rss-parser
import { findCanonical } from 'feedcanon'
import Parser from 'rss-parser'
const rssParser = new Parser()
const url = await findCanonical('https://example.com/feed', {
parser: {
parse: (body) => rssParser.parseString(body).catch(() => undefined),
getSelfUrl: (feed) => feed.feedUrl,
getSignature: (feed) => {
return JSON.stringify({
title: feed.title,
items: feed.items?.map((item) => item.guid),
})
},
},
})