I'm considering moving tailwindcss to a peer dependency, pinned to the current major release version.
As v3 minor releases of Tailwind shouldn't impact anything this plugin does, this allows a bit more freedom for those using the plugin to upgrade/downgrade Tailwind as they see fit independent of the plugin itself.
On a purely selfish basis, this also avoids me having to increment the plugin when a new minor release comes out, I would just need to road test major versions if/when they are released.
Unless anyone can think of a compelling reason to not do this, I'll look to implement this in the next few weeks.
I'm considering moving
tailwindcssto a peer dependency, pinned to the current major release version.As v3 minor releases of Tailwind shouldn't impact anything this plugin does, this allows a bit more freedom for those using the plugin to upgrade/downgrade Tailwind as they see fit independent of the plugin itself.
On a purely selfish basis, this also avoids me having to increment the plugin when a new minor release comes out, I would just need to road test major versions if/when they are released.
Unless anyone can think of a compelling reason to not do this, I'll look to implement this in the next few weeks.