Is there a way to Auto-fix the suggestCanonicalClasses warning for the entire project?

[Kentakoong]

Hi, I'm currently using both Zed and VSCode intellisense, and I would like to know if I could auto fix these errors?

[rozsazoltan]

Maybe the upgrade tool fixes it? (Run it strictly on a new branch to avoid any data loss.)

• https://tailwindcss.com/docs/upgrade-guide#using-the-upgrade-tool

[jthrilly]

The upgrade tool does indeed fix it (thanks for the tip!).

However, I think it would be brilliant to have better IDE integration for autofixing this category of problem. It looks like it would require a completely different implementation approach though. Either an eslint plugin (😬) or adding an LSP source.fixAll.tailwindCSS code action so we can configure VS Code editor.codeActionsOnSave to auto‑fix all Tailwind diagnostics on save (similar to ESLint’s source.fixAll.eslint).

Is there a better solution?

[Kentakoong]

Yep, this does fix it, thanks. Though like @jthrilly said, would be a great ideas if linters could implement a way to fix it.