Is it possible to do a template-only upgrade?

[jagthedrummer]

I work on a project that is more-or-less just a collection of .html.erb templates that are intended to be used within a Rails project that has tailwind installed. None of the normal config files exist in this project, so when I run the upgrade tool it immediately complains about the missing files and then exists. Is there a way to tell the upgrade tool to skip all of the config migration bits and to only update a directory full of templates from the old syntax to the new syntax?

[sercanvr]

I work on a project that is more-or-less just a collection of .html.erb templates that are intended to be used within a Rails project that has tailwind installed. None of the normal config files exist in this project, so when I run the upgrade tool it immediately complains about the missing files and then exists. Is there a way to tell the upgrade tool to skip all of the config migration bits and to only update a directory full of templates from the old syntax to the new syntax?

Hello jagthedrummer,

That's a very specific and interesting use case. You're right, the official @tailwindcss/upgrade tool is not designed to handle a templates-only migration. It requires the configuration files to be present as it's intended for a complete project upgrade.

Unfortunately, the tool does not have a flag or option to skip the config migration part and only handle the templates.

For this kind of project structure, the most effective way to upgrade would be to use a project-wide find-and-replace tool or a simple script to handle the syntax changes directly in your .html.erb files.

Hope this helps!