[jest/vitest] Duplicate imports added during partial migration

[codemod-com-bot]

Faulty codemod

filed on behalf of @Stanzilla

It looks like the migration does not check for existing imports of vitest before adding new ones, means if you are in the middle of a partial migration it keeps adding new imports at the top of every file

https://github.com/codemod-com/commons/tree/main/codemods/jest/vitest

Estimated impact

Numbers about your specific codemod run:

• Total number of files/instances transformed: X
• Number of files/instances missed by the codemod (FN): X
• Number of files/instances mistakenly transformed (FP): X

Anything else that helps the community prioritize, e.g.:

• I still need this fix for my current or upcoming migration.
  OR
• I manually fixed my issue, but I'm reporting this for other community members.
  ert the contents of a log file generated by the codemod run here.

Additional context

Add any other context about the problem here. This might include the target project, an explanation of the faulty output related to business logic, relevant links, etc.

[alexbit-codemod]

thanks for reporting this issue @Stanzilla.

i share this with the community to see if someone can pick this up.

cc @vladdenisov who also created another codemod for this migration. (https://codemod.com/registry/jest-to-vitest)

[Stanzilla]

thanks for reporting this issue @Stanzilla.

i share this with the community to see if someone can pick this up.

cc @vladdenisov who also created another codemod for this migration. (codemod.com/registry/jest-to-vitest)

Hey, thanks! That one seems to have the same problem:

[alexbit-codemod]

Got it! thanks for checking

Was duplicate import the only issue with the original codemod?

Also, if you can share more about your use case and the potential impact, it could help encourage the community to prioritize this task. (I shared the template in the task description.)

[Stanzilla]

Got it! thanks for checking

Was duplicate import the only issue with the original codemod?

Also, if you can share more about your use case and the potential impact, it could help encourage the community to prioritize this task. (I shared the template in the task description.)

I'm migrating a package in a monorepo from Jest to Vitest, trying different things to evaluate what the best way is to do it for the whole monorepo.

I think it was the only issue but I might be remembering wrong, I tried a few different tools. One thing I remember doing manually was changing type jest.Mock to Mock and importing that from vitest, that might not be covered by codemod.

[Stanzilla]

@alexbit-codemod going to attempt a migration again soon, any more info you need here?

[alexbit-codemod]

Awesome to hear from you Ben.

The bad news is we don't improve legacy codemods built with our old tooling.
The good news is we have a brand new AI-powered https://codemod.studio built on top of ast-grep, plus an open-source CLI: https://go.codemod.com/cli-docs

For paid customers, we’ve got some solid pro codemods too, like Jest to Vitest.

Book a time if you wanna see a demo of both the OSS and paid stuff: https://cal.com/alexbit

[alexbit-codemod]

in our new studio, you can dry-run your codemods on your github repos.

and with the same codemod that you automate migration, you can also keep track of the progress per team and over time.

[alexbit-codemod]