Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update dependencies to use tailwind v3.0 #223

Closed
nickt26 opened this issue Dec 12, 2021 · 5 comments
Closed

Update dependencies to use tailwind v3.0 #223

nickt26 opened this issue Dec 12, 2021 · 5 comments

Comments

@nickt26
Copy link

nickt26 commented Dec 12, 2021

No description provided.

@evdama
Copy link

evdama commented Feb 8, 2022

any news on this? 😃

@jonaskay
Copy link
Owner

Sorry for the late answer. I will be doing some bigger updates during this summer and this update is a high priority.

@hillin
Copy link

hillin commented Jun 17, 2022

Would expect this too, it works well with tailwindcss 3.x, it's just a little bit annoying everytime we run yarn, it complains

[email protected]" has incorrect peer dependency "tailwindcss@^2.0.1".

@zaclimon
Copy link

zaclimon commented Dec 4, 2022

Is there any news? 👀 I know that we could still bypass the issue by using the --legacy-peer-deps option, but installing 2 versions of tailwind is not the best solution.

Perhaps as a stopgap measure, the plugin could be updated for Tailwind 3 and then if there are some bigger features in the roadmap, then they could follow suit. What do you think @jonaskay?

@jonaskay
Copy link
Owner

jonaskay commented Mar 1, 2023

Hi! I'm very late with this but a new version is out: https://github.com/jonaskay/tailwindcss-elevation/releases/tag/v2.0.0

Please note that this update introduces breaking changes to how options are passed to the plugin. You will find new instructions in the README. Basically the plugin is now following the current Tailwind CSS instructions for passing options to plugins.

@zaclimon thank you for your suggestion! I have postponed bigger changes to get this update out.

@jonaskay jonaskay closed this as completed Mar 1, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants