Filip Sodić

@Martinsos The rendering isn't postponed, it never happens.

I've come to recent discoveries here, so I'm moving it back to "no status" to discuss during sprint planning. Reference: Effective Typescript, 2nd edition, item 55

> That is peculiar! Might it mean that one of the deps updated minor version and caused this that way? The error is only triggered when you import an operation...

More motivation: https://discord.com/channels/686873244791210014/867713251479519232/1237475645290971136

Hi @napon, thanks for reporting! Just to ensure I got it right, you're talking about "too many files being watched" issue?

Hmm, I gotta admit I'm not familiar enough with the tools used to debug these kinds of issues, so I wouldn't know what to ask for. @napon Any chance you'd...

User hitting this: https://discord.com/channels/686873244791210014/1290413532772564992/1290413532772564992

We should take care of this before the next release right? Btw, does it work with 0.16.4?

https://github.com/wasp-lang/wasp/pull/2054 took care of some of the flags, but not all of them (e.g., the one which motivated this issue, `strictNullChecks` is still off). The remaining flags are already explicitly...

`strictNullChecks` was enabled in https://github.com/wasp-lang/wasp/pull/2360. Just a few more to go! This one might be close: https://github.com/wasp-lang/wasp/issues/2056