mscdex

Also, does simply commenting out the offending line out fix the issue or cause other problems? It would be interesting to know what the `status` value is when it's not...

Currently network devices are always opened in promiscuous mode.

There is an example in the readme that shows how to decode some of the low level protocols. Is this what you're using? Is it possible that that packet is...

@RikuRuokonen Lodge an issue with the `graphql-upload` project owners to update their `busboy` dependency.

@nathan-gilbert If you're just parsing web forms (multipart or urlencoded), `busboy` would be a better choice. `dicer` was originally created for use by `busboy`, but it no longer depends on...

@nathan-gilbert If the parent dependency is an older version of `busboy`, releasing a new version of `dicer` would not help as those old versions of `busboy` used exact versions for...

@nsandeepn `multer` just needs to upgrade to the latest version of `busboy`. For existing `multer` installations, there's nothing that can be done (see https://github.com/mscdex/dicer/pull/22#issuecomment-1133276609).

@Kondamon It's low priority at the moment. `dicer` really needs a rewrite, much like `busboy` had, because node streams have come a long way since I first wrote the modules.

This module is due for a rewrite now that node should have all of the necessary hooks to accomplish what the hacks were previously doing. I'm not sure when that...

What I had in mind was just removing the event hacks, using ES6 Classes, and other code cleanup (that doesn't cause noticeable performance regressions).... nothing breaking.