No post body was provided.
Untitled topic
1–10 of 21 posts
Re: undefined
#2I can definitely relate. As an engineering manager, migration projects are often the least fun to work on. They are complex, take a ton of time and no one wants to work on them. If this works as promised. I would like to try it on a few migrations myself. Best of luck on your work,
Re: undefined
#3I can definitely relate. As an engineering manager, migration projects are often the least fun to work on. They are complex, take a ton of time and no one wants to work on them. If this works as promised. I would like to try it on a few migrations myself. Best of luck on your work,
Yea! Let me know if we can help your team with any of those. Right now we specialize in AngularJS -> React, CRA -> Next, JS -> TS, and Upgrade Next
Re: undefined
#4I can definitely relate. As an engineering manager, migration projects are often the least fun to work on. They are complex, take a ton of time and no one wants to work on them. If this works as promised. I would like to try it on a few migrations myself. Best of luck on your work,
How do you handle dependencies like libraries?
Re: undefined
#5I can definitely relate. As an engineering manager, migration projects are often the least fun to work on. They are complex, take a ton of time and no one wants to work on them. If this works as promised. I would like to try it on a few migrations myself. Best of luck on your work,
How do you handle dependencies like libraries?
We use LangChain to crawl documentation and code examples for relevant frameworks and libraries, to make sure that the AI generated PR is up-to-date. We also have a custom dependency resolver that detects which new dependencies need to be added, as well as updating the package.json files with the correct version numbers
Re: undefined
#6Earlier quoted context omitted.
How do you handle dependencies like libraries?
We use LangChain to crawl documentation and code examples for relevant frameworks and libraries, to make sure that the AI generated PR is up-to-date. We also have a custom dependency resolver that detects which new dependencies need to be added, as well as updating the package.json files with the correct version numbers
"custom dependency resolver" I am intrigued, Ill check it out.
Re: undefined
#7I've seen a team crawl through a Python 2 -> 3 migration for months, paralyzing product dev. Applying AI to the migration space is really smart.
Re: undefined
#8I've seen a team crawl through a Python 2 -> 3 migration for months, paralyzing product dev. Applying AI to the migration space is really smart.
Yea! It turns out that we get this request quite often (Python 2 -> 3). It's on the roadmap.
Re: undefined
#9Earlier quoted context omitted.
We use LangChain to crawl documentation and code examples for relevant frameworks and libraries, to make sure that the AI generated PR is up-to-date. We also have a custom dependency resolver that detects which new dependencies need to be added, as well as updating the package.json files with the correct version numbers
"custom dependency resolver" I am intrigued, Ill check it out.
In general, as our AI agents produce code files, we collect dependencies, and then at the end, use npm to determine the correct version numbers without actually installing on disk
Re: undefined
#10How is this better than deterministic codemods?
Next 12 to 13 (with app router) is a struggle for even seasoned teams. Not looking forward to AI handing off a 162833292 line PR.