Charmander

I think a limit example should demonstrate more than attaching a listener to the event that’s already documented. How about covering the necessary error handling and cleanup?

Also makes checking for malicious code easier

You don’t seem to be writing anything into the busboy instance. ```js req.pipe(busboy); ```

Reusing arrow functions’ arrow works very well for most purposes, but not for `await`.

> This module encodes a string to look like a UTF-8 string, which may be used for online UTF-8 demos, but as far as bytes are concerned, which is important...

> distutils.errors.DistutilsPlatformError: Microsoft Visual C++ 14.0 is required. Get it with "Microsoft Visual C++ Build Tools": https://visualstudio.microsoft.com/downloads/

`--ro-bind path/to/file /where/to/mount/it`

I don’t see why the reason for the hardening would only apply to privileged bwrap.

What if the data bubblewrap is parsing is the problem (i.e. untrusted), not the program passing it through?

> Some programs outside container delete DEST and create a new one. If you can make them delete DEST’s contents and not DEST itself, that’s usually a good fix.