feat(req-param): migrate req-param to codemod.com

[bjohansebas]

New codemod migrated to use ast-grep and will be published soon on the codemod.com platform

[bjohansebas]

Basically, this code is repeated from the previous codemods, probably could be factored out into a utils package, though I'm wondering how this would behave for codemod registration, being a separate package and not published to npm

[AugustinMauroy]

a local npm workspace will be bundled by the codemod cli.

!the ci have to npm I before publish!

[bjohansebas]

By the way, I'm setting this to private so we don't accidentally publish this to npm, but does this affect codemod registration?

[AugustinMauroy]

codemod cli don't care about package.json

[AugustinMauroy]

okay on userland migration we require some test around import idk what do you want but here the list

• cjs
• cjs destructred
• esm dynamic import with const foo = await import and in C.B.
• esm alias

[AugustinMauroy]

I'm not sure of the naming because it's too general. So it's may confuse user

[bjohansebas]

Naming codemods is just as hard as naming variables, a difficult decision.

I’ll think about other names.

[AugustinMauroy]

BTW I use gh copilot for that question and not same too bad. if you want I have gh pro for free as student I can ask.

[bjohansebas]

Yeah, i also have github pro for free as a student. i’ll ask them for some good name suggestions.

[bjohansebas]

explicit-request-params? req-param-migration?

[bjohansebas]

okay on userland migration we require some test around import idk what do you want but here the list

I don’t quite understand what you mean by the imports. We don’t need to modify imports here in the codemods.

[AugustinMauroy]

okay on userland migration we require some test around import idk what do you want but here the list

I don’t quite understand what you mean by the imports. We don’t need to modify imports here in the codemods.

Oh right, my bad just simple ESM should work 😅

[AugustinMauroy]

LGMT !