mscdex
mscdex
@ruur Are you closing this because the issue was created in error? Otherwise it should stay open if it's an issue that exists in the master branch.
I'm not sure what the problem is. Once a part has started, data is just passed on through, so you should get any partial data. The only thing is that...
IIRC that's more or less what is used in `formidable`/`multiparty`, just parted out into its own module.
I suppose so, but AFAIK the underlying algorithms haven't really changed in `dicer`, `multiparty`, or `formidable`. I'm not sure about the other modules.
- **node-methods**: it's just exporting a small array, so it's not a big deal. IMHO it's worth not pulling in another dependency just for that. _shrug_ - **path-match**: one of...
`querystring` was modified from node core to separate out the try-catch in `querystring.parse()`. `path-join` is basically the posix `path.join()` from node core, simplified a bit. The two reasons for this...
@toots Any chance of getting this fixed? I'm currently having to manually change Buffer.isBuffer() to use util.isBuffer()'s logic (similar to @thlorenz's workaround) because require('stream').Readable uses Buffer.isBuffer() in chunkInvalid() and that...
I think this may be related to substack/node-browserify#513 in which two copies of Buffer are injected into bundles.
ASCII-compatible means bytes 0x00-0x7F in an encoding are all ASCII characters/bytes and not some other characters. Many character sets are compatible in this way, but some are not. Checking whether...