Jimmy Wärting
Jimmy Wärting
0.85% now 😄
there is quite many more chains of require calls in the readme
It would be cool to see debug being a ESM only package, It would put pressure on many packages towards upgrading their commonjs packages to ESM as well and benefit...
we should at least discourage this antipattern `var debug = require('debug')('http')` it's bad to call/chain require, it only makes it harder for those who wish to swtich to esm at...
oh, grate just what i wanted... transpiling it to another a bloated-overhead-language-that-do-not-work-in-any-enviorment-without-being-transpiled-to-javascript-first syntax...
The body-parser don't really to the same thing. the body-parser is a middleware that blocks the actual route handler that it should call after you have received the hole body....
Yeay, then I could take advantage of [fetch-blob/from.js](https://github.com/node-fetch/fetch-blob#blob-part-backed-up-by-filesystem) methods that can retrieve a Blob/File from the file system. or use undici or node-fetch `await res.blob()` even If you would accept...
> > We don't currently use async functions in express core. > > Maybe because no pr can use async functions before this pr lands? Word!
+1 for `require('https').request` if it's just one simple post request. looking into ways to reduce my sub dependencies - thats why i'm here
Don't seem to be the only one wanting to port closure compiler to wasm 😉 subscribing to this issue. ping me @jespertheend if you ever release a wasm version of...