Jake Verbaten

I was able to solve the OOM issue for myself with ```sh NODE_OPTIONS=--max-old-space-size=8192 tsc ```

My OOM complaint is not a regression per se, just an artifact of a large codebase, I had multiple different versions & copies of the entire `aws-sdk` v2 library loaded...

How can I turn this feature on and off at runtime ? I would love to be able to do ```js new PrismaClient({ log: ..., datasources: ..., jsonProtocol: isStaging ?...

This library is deprecated / unmaintained, please use another one.

For my personal use case I am likely to copy paste the source code of `preact` into my application and use it directly so that I can have the unminified...

I guess having `dist/preact.raw.js` next to `dist/preact.min.js` would also help me, in that I can quickly and easily copy the raw single file source code or import it with `require('preact/dist/preact.raw.js')`...

I appreciate the technical explanation of why this wouldn't work with the ecosystem and the devtools. I am however completely blown away that this technical limitation exists. it boggles my...

The consistent mangling for ecosystem I can understand. Would be nice if the ecosystem respects both the unmangled and mangled property names, so I could use either the min or...

The solution I identified was to manually add the following lines to my test suite at the top of `test/index.js` ``` require('source-map-support').install({ hookRequire: true }); ``` Then running `nyc` it...

``` raynos at raynos-Precision-5530 ~/optoolco/_op-sdk on master* $ npr nyc -a -r html -- node test/index.js TAP version 13 # setup # sync upload /home/raynos/optoolco/_op-sdk/src/helpers/concurrent-queue/index.js:13 throw new Error('whoop') ^ Error:...