It's covered by https://eslint.vuejs.org/rules/no-deprecated-destroyed-lifecycle.html so I think we can skip this in vue-codemod.

Hi @sodatea , it is true that some rules can be fixed by eslint-plugin-vue, but vue-codemod is a code transform tool, these fixes of eslint should also be the responsibility of vue-codemod. In addition, users do not need to configure eslint (if eslint has not been configured in the project).

In my fork repo originjs/vue-codemod, we use vue-eslint-parser to parse the template and rewrite a set of utils for modifying the template block based on the idea of modifying the source code of eslint, which makes vue-codemod more powerful. We veried some open-source projects and found that the average transformation rate reached nearly 80%. With some manually modification, Vue 2 project may upgrade to Vue 3 successfully.

For details, please see user guide. We also provided a typical upgrade case.

I wonder if above implementation meets your expectations? if so, I'm happy to contribute the code to vuejs/codemod.