Open LukasTy opened 1 month ago
I would say that this is not a bug but an enhancement to make the error better.
I would say that this is not a bug but an enhancement to make the error better.
For json files—I completely agree, but failures on ts
files are a bit strange—they are on typing lines. 🤷
Steps to reproduce
Link to live example: (required)
Steps:
npx @mui/codemod@next v6.0.0/styled packages
on the latestmui-x
master branchCurrent behavior
A few example errors:
Expected behavior
Codemod does not produce the above errors, but ignores the code that it does not need to transform.
Context
No response
Your environment
``` System: OS: macOS 14.5 Binaries: Node: 18.20.2 - ~/.nvm/versions/node/v18.20.2/bin/node npm: 10.5.0 - ~/.nvm/versions/node/v18.20.2/bin/npm pnpm: 9.6.0 - ~/.nvm/versions/node/v18.20.2/bin/pnpm Browsers: Chrome: 127.0.6533.89 Edge: 127.0.2651.86 Safari: 17.5 npmPackages: @emotion/react: ^11.13.0 => 11.13.0 @emotion/styled: ^11.13.0 => 11.13.0 @mui/icons-material: ^5.16.5 => 5.16.5 @mui/internal-markdown: ^1.0.8 => 1.0.8 @mui/internal-test-utils: ^1.0.5 => 1.0.5 @mui/material: ^5.16.5 => 5.16.5 @mui/monorepo: github:mui/material-ui#4a82b6b0e0395db8fa0a0d49b6b76de4516b1579 => 6.0.0-beta.4 @mui/utils: ^5.16.5 => 5.16.5 @types/react: ^18.3.3 => 18.3.3 react: ^18.3.1 => 18.3.1 react-dom: ^18.3.1 => 18.3.1 typescript: ^5.5.4 => 5.5.4 ```npx @mui/envinfo
Search keywords: codemod, styles