would be great to review if possible@danieldelcore 🙏

Really interesting, could you give me some more background as to how this all fits together? As I understand it, instead of only being able to modify js / ts files you want to be able to provide a custom runner to begin to support other types of files like css?

Can you share an example codeshift.config with me?

Also i've just merged some fixes/improvements, you might want to rebase 😄

@danieldelcore hey! yes, correct, we want to have independance from upstream (you) so that we don't need to wait to get some custom runner merged (sometimes it could be very specific even, and you might not even need it merged, and that's fine), while still utilizing your CLI w/o publishing our own, and this unlocks the door.

this could even be used if e.g. you want to do more steps before/after the codemod run, e.g. doing some pre-processing, or idk updating some npm dependencies -- you can basically add any code there. the value is that we don't need to create wrapper CLIs around it, and just use the @codeshift/cli as it is.

re: updates -- coolio, rebased smoothly.

an example I already linked to --https://github.com/pipedrive/CodeshiftCommunity/pull/22

• codeshift.config.js:https://github.com/pipedrive/CodeshiftCommunity/blob/0f9fa7119abdc7afcd38022a7a235cf433be0030/community/%40pipedrive__convention-ui-react/src/codeshift.config.js
• the custom runner, for postcss this time:https://github.com/pipedrive/CodeshiftCommunity/blob/0f9fa7119abdc7afcd38022a7a235cf433be0030/community/%40pipedrive__convention-ui-react/src/misc-utils/runPostcssCodemod.ts
• & how we use the custom runner (by specifying thecodeshiftConfig):https://github.com/pipedrive/CodeshiftCommunity/blob/0f9fa7119abdc7afcd38022a7a235cf433be0030/community/%40pipedrive__convention-ui-react/src/5.0.0/codemod.postcss.ts

and you can read on how to use the codemods (we have a simple wrapperrun.js which by now the only unique functionality it has isshorthands.json; run.js is also the reason why i asked to change the config from .ts to .js! though, somecommunity/ packages here still use the non-cjsexport default instead ofmodule.exports =. and it's also the reason why we got rid ofrequire.resolve orpath.resolve inside ofcodeshift.config.js, and would recommend applying this to packages here as well. (the config becomes almost like a json file at this point)):

• https://github.com/pipedrive/CodeshiftCommunity/tree/fork/community/%40pipedrive__convention-ui-react#readme

you can try running the demo files. i just added a new one for scss:

• https://github.com/pipedrive/CodeshiftCommunity/tree/fork/community/%40pipedrive__convention-ui-react/src/5.0.0/demo

the only concern is -- will this work if we publish our npm package? i haven't had a chance to try that; i need to first extract into a separate repository. but ideally we'd figure this out here before i do that.

and maybe a slight change i'd do is renamingcodeshiftConfig to justcodemodsConfig orcodemodConfig or both. goes in line with the same idea that we should have an npm packagecodemods-cli that you couldnpx to, instead of@codeshift/cli.

wdyt? would be very useful.