Jeff Robbins

There is a pull request that you can test and help improve so we can get Webpack5 support: https://github.com/herberttn/bytenode-webpack-plugin/pull/7

Okay. I think I've got all of the tests in place now. However, I think that this may have surfaced few bugs/problems/incompatibilities between the `web-midi-test` library and `webmidi`. Some theories:...

Status of tests: - [x] Enumerations - [x] Forwarder - [ ] Input - the `midiSrc.emit()` problem is causing a lot of timeouts since `.addListener()`s aren't triggering - [ ]...

> Thanks for your work on this Jeff. Unfortunately, as I mentioned in a prior message, I don't have much bandwidth to dedicate to this right now. Are you currently...

I think I've found the timestamp problem and I've posted an issue for the `web-midi-test` project: https://github.com/jazz-soft/web-midi-test/issues/2 But now that I'm looking at [the spec](https://webaudio.github.io/web-midi-api/#dom-midioutput-send) again, maybe this isn't the...

I've tested 1.3.5 in both via the Mocha tests in the `bytenode` repo and via `electron-bytenode-example`. I can't replicate this error. Maybe @OsamaAbbas will have an idea. But is there...

It looked like this got in for 6.4.8 👍, but now it's gone again for 6.4.9 😕. What happened?

Oh. Okay... here it is: https://github.com/EventEmitter2/EventEmitter2/issues/292

Here's what I'm currently doing: ``` javascript function isGpioAccessible() { let fd; try { fd = fs.openSync('/sys/class/gpio/export', 'r+'); } catch(e) { return false; } finally { if (fd) { fs.closeSync(fd);...

This is great! Makes much more sense now.