Unable to execute upgrade@next #15704
Replies: 2 comments 4 replies
-
Seems like it could be one or both of the Tailwind plugins you have. You could try commenting out/removing them and see if the migration goes better. |
Beta Was this translation helpful? Give feedback.
4 replies
-
Due to time contraint, I decide to close this discussion and upgrade manually. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Hi,
I'm having difficulty moving to version 4, whenever I execute npx @tailwindcss/upgrade@next, I'm getting the following.
For context purposes, we were running Tailwind 2.2.4, about a month ago, we upgraded to version 3, then this week we saw version has become available, therefore we try to upgrade to version 4.
`tailwindcss v4.0.0
│ Searching for CSS files in the current directory and its subdirectories…
│ ↳ Linked
./tailwind.config.js
to./src/css/index.css
│ Migrating JavaScript configuration files…
│ ↳ Could not load the configuration file: variants is not a function `
However I do not have @Variants in my ./tailwind.config.js
Environment details:
Node.js: v22.12.0
npm: 10.9.0
Tailwind CSS: ^3.0.0
PostCSS: 8.5.1
OS: Mac OS (Apple Silicon)
Related Files
tailwind copy.config.js.txt
index.css.txt
Beta Was this translation helpful? Give feedback.
All reactions