Investigate how our file watching works

[sodic]

With Wasp 0.12.0 and the restructuring (#1688), we've removed the constraint of separating server files from client files.

We should investigate the impact this had on our watching procedures and hot reloads.

Goals:

• The server rebuilds only on changes that affect the server framework code.
• The SDK rebuilds only on changes that affect the SDK code.
• The web app rebuilds only on changes that affect the web-app framework code.

Questions, on each change, what does:

• Nodemon watch?
• TSC compile (in SDK)?
• Rollup rebuild?
• Vite watch?
• Vite rebuild?

Relevant context:

• Restructuring prototype RFC #1584 (comment)

Relevant todo in the code:

wasp/waspc/src/Wasp/Analyzer/Evaluator/Evaluation/TypedExpr/Combinators.hs

Line 176 in f2721e7

-- Filip: We no longer want separation between client and server code

[Martinsos]

We also seem to be having an issue with too many files being watched with the recent projects, check out this issue: #1919 .

This might be because we have some files being watched redundantly.

There are commands that track how many files are watched by which process, so we should se that to observe what is happening.

[napon]

I'm running into this issue in my project. Let me know if you need me to share any logs to help debug the issue further!

[sodic]

Hi @napon, thanks for reporting!

Just to ensure I got it right, you're talking about "too many files being watched" issue?

[napon]

Yes that's right

[sodic]

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 be ready to share your project with me and let me play around with debugging it locally?

[infomiho]

Related issue: #1843