Use feedr to fetch the data from a remote url, respect its caching, and parse its data. Despite its name, it's not just for feed data but also for all data that you can feed into it (including binary data).
Use feedr to fetch the data from a remote url, respect its caching, and parse its data. Despite its name, it's not just for feed data but also for all data that you can feed into it (including binary data).
npm install --save feedrrequire('feedr')This package is published with the following editions:
feedr aliases feedr/source/index.jsfeedr/source/index.js is esnext source code with require for modulesEnvironments older than Node.js v8 may need Babel's Polyfill or something similar.
// Create a new feedr instance
const feedr = require('feedr').create({/* optional configuration */})
// Prepare our feeds that we want read
const feeds = {
someAtomFeed: 'https://github.com/bevry/feedr/commits/for-testing.atom'
someJsonFile: 'https://raw.githubusercontent.com/bevry/feedr/for-testing/package.json'
}
// Read a single feed
feedr.readFeed(feeds.someAtomFeed, {/* optional configuration */}, function (err, data, headers) {
console.log(err, data, headers)
})
// Read all the feeds together
feedr.readFeeds(feeds, {/* optional configuration */}, function (err, result) {
console.log(err, result.someAtomFeed, result.someJsonFile)
})
Feed configuration defaults / global configuration properties are:
log defaults to null, log function to usetmpPath defaults to system tmp path, the tempory path to cache our feedr results tocache defaults to one day 1000*60*60*24, available values:
Number prefers to use the cache when it is within the range of the number in millisecondstrue prefers to use the cache when the response headers indicate that the cache is still valid"preferred" will always use the cache if the cache existsfalse will never use the cachexml2jsOptions defaults to null, the options to send to xml2jsrequestOptions defaults to null, the options to send to requestFeed configuration properties are:
url required, the url to fetchhash defaults to hash of the url, the hashed url for cachingname defaults to hash, the name of the feed for use in debuggingpath defaults to tmp feed path, the path to save the file toparse defaults to true, whether or not we should attempt to parse the response data, supported values are xml, json, cson, yaml, string, raw/false. If true will try all the available parsers. Can also be a function with the signature ({response, data, feed, feedr}, next(err, data))check defaults to true, whether or not we should check the response data for custom error messages. Can also be a function with the signature ({response, data, feed, feedr}, next(err))xml2jsOptions defaults to global value, the options to send to xml2jsrequestOptions defaults to global value, the options to send to requestDiscover the release history by heading on over to the HISTORY.md file.
Discover how you can contribute by heading on over to the CONTRIBUTING.md file.
These amazing people are maintaining this project:
No sponsors yet! Will you be the first?
These amazing people have contributed code to this project:
Discover how you can contribute by heading on over to the CONTRIBUTING.md file.
Unless stated otherwise all works are:
and licensed under:
v4.8.0 2019 December 9
FAQs
Use feedr to fetch the data from a remote url, respect its caching, and parse its data. Despite its name, it's not just for feed data but also for all data that you can feed into it (including binary data).
The npm package feedr receives a total of 47 weekly downloads. As such, feedr popularity was classified as not popular.
We found that feedr demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 2 open source maintainers collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Research
Security News
Socket researchers uncover a malicious npm package posing as a tool for detecting vulnerabilities in Etherium smart contracts.
Security News
Research
A supply chain attack on Rspack's npm packages injected cryptomining malware, potentially impacting thousands of developers.
Research
Security News
Socket researchers discovered a malware campaign on npm delivering the Skuld infostealer via typosquatted packages, exposing sensitive data.