(frontend): Incremental migration to svelte 5

[sm17p]

Migration Plan step by step

• Turn on dynamicCompileOptions for vite-plugin-svelte, and add files in the runes whitelist (runesGlobs)
• Run the migration script for whitelisted files
• Fix svelte/legacy depracation warnings (Avoiding createBubbler over here)
• Once all the components are runes compatible, start chiping away the remainingsvelte/legacy compat bindings
• Add commits to .git-blame-ignore-revs for a cleaner git blame

---

Following the svelte 5 migration guide

---

Known Issues

• patchWidgetLayout doesn't update deeply nested properties reactively - 3e572c9
• Graph.svelte (Node Graph) is invisible on load, displays after clicking on screen - 055b6f3 autofixed when rebased onto master
• NodeCatalog.svelte reactive bindings messed up for sub-menus and node creation - 461aa77
• FieldInput does not reset local component state when hit with Escape - d24c0b6

[sm17p]

@Keavon I've enabled runes mode for the whole project with the last commit, but still testing it. Let me know if you find anything that's breaking

[Keavon]

Thanks. Please keep testing it extensively and do any polishing you find 'til I get the chance to code review this. There are a few PRs in front of yours in the priority queue so it might be a couple of days, but I'll try my best to keep it from taking too long.

[sm17p]

I'm done with my bug fixes ✌️. Let me know if anything else is breaking as I'm not well aware of the UI hot paths and user workflow

[Keavon]

Could you please sync this with master?

[sm17p]

Synced!

[Keavon]

Once again please, sorry for the trouble!

[sm17p]

Once again please, sorry for the trouble!

No worries, have synced it again

[Keavon]

Could you please update it again? I think I'll be able to get to it today since it is finally roughly next in my queue.

[sm17p]

Synced! I noticed backend behaviour has changed?

Undo doesn't work like before. I tried it onfill property and it behaves differently on editor.graphite.rs and dev.graphite.rs. Suspecting a regression in backend code

[Keavon]

Thanks! What is the fill property you are referring to? The solid color given to the Fill node? From my brief comparison with master and editor, it seems they work the same. So I'm probably misinterpreting what you are discussing. Is that something where you could give some detailed reproduction steps in a newly filed issue, please? I assume that was just an observation and not tied to this Svelte upgrade specifically, right?

[sm17p]

This is the editore.graphite.rs vs dev.graphite.rs comparision for undo.

1. Editor - Circle color undo's on first attempt
2. Dev - Circle color doesn't not change even after repeated attempts, (guess is all the color updates from picker are sent to the backend which creates a long undo queue)

Correct me if I'm wrong, but dev is deployed from master branch? If yes, then this might not be related to the migration code

editor_VS_dev_UNDO_behaviour.mp4

[Keavon]

Yes, dev deploys master.

[Keavon]

!build

[github-actions]

📦 Build Complete for 46ce377
https://00702c79.graphite.pages.dev

[Keavon]

What was the reason for needing to rename messages.ts to messages.svelte.ts?

[sm17p]

I'm gonna do a final round of testing by tonight after syncing with master. If I don't find any issues, then I'll reopen from draft again for review

[sm17p]

I'm done with my testing, with d24c0b6FieldInput has two different behaviours

1. When attached with an oncommitText callback, it works in local edit mode allowing users to discard editing state on Esc
2. Without it, it's directly bound and edits are reflective of the current state value

---

Aside from last bug, no new bugs have been found and therefore I'm re-opening for a review ✌️

[sm17p]

@Keavon can we build and push this for testing?

[Keavon]

!build

[github-actions]

📦 Build Complete for d24c0b6
https://ee9b3112.graphite.pages.dev

[sm17p]

There's one task remaining which is adding the .git-blame-ignore-revs. About that, it'd be better to add in a separate PR on a need basis as the project sees fit.

Aside from that, I feel confident with the build.

I'd prefer a merge this Friday or Saturday, as I'd be available to provide with any fixes if needed anytime after that