[infra] Can't pass --jscodeshift option to codemod

[Janpot]

Steps to reproduce

Steps:

1. Run pnpm dlx @mui/[email protected] v8.0.0/preset-safe <path> --jscodeshift "-v"
2. Check the jscodeshift command that is being executed

Current behavior

no -v option is added to the command

Expected behavior

a -v option is added to the command

Context

Trying to figure out why so many files are being transformed, I feel like it's running on too many files. Trying to get more visibility on what's being passed to jscodeshift and more control over which paths to ignore.

Your environment

npx @mui/envinfo

  System:
    OS: macOS 14.6.1
  Binaries:
    Node: 20.18.3 - ~/.nvm/versions/node/v20.18.3/bin/node
    npm: 10.8.2 - ~/.nvm/versions/node/v20.18.3/bin/npm
    pnpm: 10.6.4 - ~/.nvm/versions/node/v20.18.3/bin/pnpm
  Browsers:
    Chrome: Not Found
    Edge: Not Found
    Safari: 17.6
  npmPackages:
    @mui/internal-docs-utils: workspace:^ => 2.0.0 
    @mui/internal-scripts: workspace:^ => 2.0.4 
    @mui/internal-test-utils: workspace:^ => 2.0.3 
    @pigment-css/react: 0.0.30 => 0.0.30 
    @types/react: ^19.0.10 => 19.0.10 
    typescript: ^5.7.3 => 5.7.3 

Search keywords: jscodeshift

[LukasTy]

@Janpot are you sure about the usage? 🤔
I tried passing jscodeshift arguments as mentioned in readme and they seem to work... 🤷 🤔

# multiple options
npx @mui/x-codemod@next v8.0.0/preset-safe docs --jscodeshift=--cpus=1 --jscodeshift=--print --jscodeshift=--dry --jscodeshift=--verbose=2

https://github.com/mui/mui-x/tree/master/packages/x-codemod#jscodeshift-options

[Janpot]

😕 Ok, I must have been doing something weird. I can make it work now. Just noticed that on our docs, it seems to be transforming the .next folder and the export folder.

[github-actions]

This issue has been closed. If you have a similar problem but not exactly the same, please open a new issue.
Now, if you have additional information related to this issue or things that could help future readers, feel free to leave a comment.

[LukasTy]

Just noticed that on our docs, it seems to be transforming the .next folder and the export folder.

Good spot. 👍
Do you think we should be doing anything about it in the codemod package? 🤔
Or just be aware ourselves?
Or document this possible gotcha? 🤔

[Janpot]

Do you think we should be doing anything about it in the codemod package?

I'm surprised it doesn't follow .gitignore. i.e. what's the purpose of transforming files that aren't checked in? Just noticed as well on packages that it includes build folders.