Update a Vue 2 Electron repo in small reviewable chunks

Kearney had Devin carry a production Electron codebase from Vue 2 to Vue 3 while refreshing dependencies and checking progress in small batches.

Done with Devin· Advanced· Dec 2024

What they did
Kearney shared a GitHub repository with Devin and asked it to modernize the app for Vue 3, including Composition API and script setup. Devin suggested a rollout plan, and Kearney signed off on replacing the state layer with Pinia. He also wanted changes committed and pushed after each group of five components, while Devin kept stopping to request approval for package edits until Kearney told it to keep moving.
How it went
Devin created a PR after about four hours and said the build was green, but it broke on Kearney's machine. They spent around two days going through fixes, yet the app still would not launch, so Kearney stopped the attempt. The effort burned through about half of his ACUs and still required manual work in every file.
Tips
Do your own local build check early instead of trusting the agent's report. If you want staged review, keep the batches small and expect dependency updates to need extra oversight.

Try it yourself with Devin

I’m giving you access to [repo name], a production Electron app built on Vue 2. Convert it to Vue 3, keep the code style aligned with Composition API and script setup, and update any npm dependencies that need to change. Work in slices of [number] components, then stop for my review before you move on. Before any irreversible action such as deleting code, changing dependencies, sending a pull request, or submitting a merge, pause and ask me to approve it. When you finish, open a pull request and summarize what you changed, which checks you ran, what still needs manual cleanup, and anything you could not complete.

Fill in the [brackets]. Agents can make mistakes, so review anything before it is sent, paid or deleted.

Get 3 agent uses like this every morning

With the day's top AI news. Free, and one click to unsubscribe.