hyper/app/notifications.js
Vladimir Starkov 3f772311db increase notification timeout up to 30m (#913)
fetchNotifications error can happen in two cases:
* https://hyper-news.now.sh is down
* you are offline

In both cases it doesn't hurt to wait half an hour.

PS. right now it hurts, when you are offline and developing
anything for Hyper, `console.error` logs the same error
every 10s and ruins your investigation.
2016-10-22 12:16:05 -07:00

39 lines
994 B
JavaScript

const ms = require('ms');
const fetch = require('node-fetch');
const {satisfies} = require('semver');
const {version} = './package';
const NEWS_URL = 'https://hyper-news.now.sh';
const matchVersion = versions => (
versions.some(v => v === '*' || satisfies(version, v))
);
module.exports = function fetchNotifications(win) {
const {rpc} = win;
const retry = err => {
setTimeout(() => fetchNotifications(win), ms('30m'));
if (err) {
console.error('Notification messages fetch error', err.stack);
}
};
console.log('Checking for notification messages');
fetch(NEWS_URL)
.then(res => res.json())
.then(data => {
const {messages} = data || {};
if (!messages) {
throw new Error('Bad response');
}
const message = messages.find(msg => matchVersion(msg.versions));
if (message) {
rpc.emit('add notification', message);
} else {
console.log('No matching notification messages');
}
retry();
})
.catch(retry);
};