Jordan Lees

Sorry but this definitely wouldn't be doable without a COMPLETE overhaul of how the entire application works from back to front. I'm not a developer of Hamsket/Rambox, but I do...

YAML is fairly complex; would builtin support add a significant amount of storage space utilization?

Test case can be simplified. Caused (somehow) by Lodash caching the native `Buffer.isBuffer` as a JS variable. ```js console.log(Buffer.isBuffer(myVariable)); // works fine let func = Buffer.isBuffer; console.log(func(myVariable)); // TypeError: Cannot...

I think this a problem with esbuild (https://esbuild.github.io) when compiling the node fallback for Assert (https://www.npmjs.com/package/assert). Investigating further...

Test case can be simplified. ```js const foo = () => foo(); foo(); // does not throw ``` ```js const foo = function () { return foo(); } foo(); //...

@DanielVain The readme says PRs with new template/examples are welcome. Create a fork, add a React with TypeScript template, and submit a PR and reference this issue #. 🙂

I suppose a dirty solution would be to: 1. First test to see if the install dir happens to already be on `PATH` 2. If not, then check for common...

Yes; `bun build file.js` results in the same `Segmentation fault`. It may be worth testing this on the Safari browser, to see if JavaScriptCore actually has protection for this kind...

Just tested it on my roommate's MacBook, in Safari's built in JS console. It manages to handle _way_ more nested `for` loops. It throws a `RangeError: Maximum call stack size...

Try "promisifying" your retrieval and callback logic: https://javascript.info/promisify Pseudo code: ```js async function test() { while(condition) { try { await promisify(); } catch {..} } } function promisify() { return...