Chung Wei Leong

Been facing the same issue for the past few months. The only workaround right now is to restart the LSPs once in a while.

I found this [PR from vtsls](https://github.com/yioneko/vtsls/pull/206). It seems Electron came with an unofficial Node version that came with pointer compression, which is also what VSCode is using. I played with...

I'm not sure if this is good enough to reproduce the problem, but if you have a really large monorepo, try opening multiple files from multiple different sub-repos, and you...

> ok, i found what was wrong in my case, zed's default memory limit is different for vtsls and typescript-language-server you can test if it's works for your case by...

Based on my experience, I don't think memory is the problem here, where one of my monorepos(about 20+ sub-repos) always uses about 5GB at max, which it doesn't even hit...

> Solution: Using Bun runtime for typescript-language-server > > This dramatically improved performance and significantly reduced RAM usage. That one of the things that I tried awhile back, unfortunately using...

This seems like a dual package hazard issue, and since RN 0.79 the `unstable_enablePackageExports` option is enable by default https://github.com/facebook/metro/pull/1448. I created a repro with Expo SDK 53, which came...

> Is there any progress or other workarounds for this? We're also seeing this issue and I'm surprised no one else is hitting it with React Native. So far based...

I haven't dove too deep into the changes, but I think it can be easily done by just changing the `ToJSON` type-util. I wrote a type utility specifically for solving...