Effects and lifecycle
Run side effects with automatic dependencies, clean them up, control ownership and flush timing, and know what runs on the server.
After this page you can write effects that track their own dependencies, split tracking from side effects, release resources on re-run and disposal, predict the exact order in which effects run, and know that none of them run on the server.