Completely agreed... I have the following (roughly) at the top of my scripts in current applications (IE is the main browser that doesn't support the features in question).
async functions and fetch...
try {
eval('(function() { async _ => _; })();');
if (typeof fetch === 'undefined') {
throw new Error('no fetch');
}
} catch (e) {
window.location.replace('/legacy.html');
}
The XMLHttpRequest API was based on the Microsoft.XMLHTTP COM library that could be used in older IE browsers starting with IE5 in 1998. Netscape (later Mozilla) added XMLHttpRequest as a native option to Gecko in 2002 and it became the norm, standardized in 2006, until fetch API became available a decade later in 2015.
Most articles that I've seen referencing the past with fetch to XMLHttpRequest tend to get muddled a bit.
https://en.wikipedia.org/wiki/XMLHttpRequesthttps://developer.mozilla.org/en-US/docs/Web/API/Fetch_API
Very nice... reminds me a lot of the windows screensaver... would be cool to use something like this as a base for a data visualizer for music playback, one of the things I really miss from the old WinAmp days when playing music.
Interesting... not sure why you would actually need a C++ (native node module) for this though... seems like just an in-process http+websocket server listening on a high port would fit the bill. Could be simpler still if coordinating with a host to arrange webrtc.
While somewhat informative, I think some things are a little bit muddied... Jest actually uses Jasmine2, and Enzyme can be integrated into several of the test tools in question. While wiring up Puppeteer can be a bit of a pain, the learning curve really isn't bad in practice.
On other problem is you have different options for different concerns. Unit testing react is not the same as integration or render testing. I happen to really like using Jest for most tests, and while I like chai/mocha more than Jasmine, Jest gives you more than just the test harness, it gives you parallel support as well as code coverage in the box.
Using Jest with puppeteer for integration/browser testing does take some work, but it's very nice in practice.
Completely agreed... I have the following (roughly) at the top of my scripts in current applications (IE is the main browser that doesn't support the features in question). async functions and fetch... try { eval('(function() { async _ => _; })();'); if (typeof fetch === 'undefined') { throw new Error('no fetch'); } } catch (e) { window.location.replace('/legacy.html'); }