Alex Coleman

cc @tbezman any update on this? Thanks

> @alex-statsig @raghavyadavm Would you mind trying out this PR? #4012 > > 1. Clone my PR > 2. `cd compiler && cargo build` > 3. There should be a...

> @alex-statsig nah I think you're good with just installing watchman. Apologies, and thanks for the help debugging. Is that intentional (and just not documented clearly) or will future versions...

> hmmm, yeah I think the only page on the docs site that mentions watchman is [here](https://relay.dev/docs/getting-started/installation-and-setup/#running-the-compiler). Yeah, and that seems to be only if using "--watch" (which I didn't...

@SooOverpowered any update on this? I'm very surprised to not see a response on here from nextjs for such a big issue. We've been chasing down memory leaks for a...

Have you just been accepting the memory leak then? The lack of response from nextjs team on issues like this astounds me 😞

This has been open for over 6 months, any update?

@ijjk @timneutkens what is the path to getting answers on this? I've been waiting for a year just to have some discussion on this, let alone reaching answers

I periodically try and dig into high memory usage in development (see many other issues such as https://github.com/vercel/next.js/issues/54708) as it causes extreme pain for many developers. It seems pinpointed to...

> I think you can do typeaheads just fine with the existing API. > > ```js > function Typeahead() { > const [search, setSearch] = useState("") > const deferredSearch =...