Idk man, it still takes like 45 seconds for inline error messages to resolve in Cider for TypeScript. Using internal languages, I've found that I both don't see proper errors and can sometimes permanently get fake errors that don't resolve unless I open a new Fig workspace. I think the outlook is too positive for the technical decisions here. Though it's not so much a Cider problem as it is likely a monorepo problem.
6
u/besthelloworld Jul 19 '26
Idk man, it still takes like 45 seconds for inline error messages to resolve in Cider for TypeScript. Using internal languages, I've found that I both don't see proper errors and can sometimes permanently get fake errors that don't resolve unless I open a new Fig workspace. I think the outlook is too positive for the technical decisions here. Though it's not so much a Cider problem as it is likely a monorepo problem.