Node-rss > Feed package change

[TBosak]

Package Changes

• Remove: rss@1.2.2 and @types/rss
• Add: feed@5.1.0

Breaking Changes

• Feed image now only supports URL string (removed metadata fields: title, link, width, height, description)
• Date fields must be Date objects (updated processDates to return Date instead of string)

New Features

• Custom extensions support for RSS 2.0 fields not natively in feed package
• managingEditor, webMaster, skipDays, skipHours now added via feed.addExtension()
• Better structured data: Author[] and Category[] objects instead of strings
• Content is now a standard field (no longer requires custom_elements)

Model Updates

• models/rss-feed.model.ts: Define local type interfaces (feed only exports Feed class at runtime)
• Extend FeedOptions and Item interfaces with mkfd-specific fields
• Updated field mappings: url→link, size→length, feed_url→id, site_url→link

Builder Updates

• utilities/rss-builder.utility.ts: Migrated to Feed class
• Web scraping and API feeds add extensions for unsupported RSS 2.0 fields
• node/imap-watch.utility.ts: Email feeds use Feed class with inline type definitions

Data Handler Fix

• utilities/data-handler.utility.ts: processDates now returns Date objects
• Added fallback to new Date() for unparseable dates
• Handles Date objects passed in (returns them unchanged)

Frontend Cleanup

• public/index.html: Removed unsupported feed image metadata form fields
• Cleaned up JavaScript references to removed fields
• Added comments documenting removed functionality

Backwards Compatibility

• Existing YAML configs continue to work without modification
• managingEditor, webMaster, skipDays, skipHours preserved via extensions
• All feeds generate valid RSS 2.0 XML

[github-advanced-security]

This pull request sets up GitHub code scanning for this repository. Once the scans have completed and the checks have passed, the analysis results for this pull request branch will appear on this overview. Once you merge this pull request, the 'Security' tab will show more code scanning analysis results (for example, for the default branch). Depending on your configuration and choice of analysis tool, future pull requests will be annotated with code scanning analysis results. For more information about GitHub code scanning, check out the documentation.