@tailwindcss/upgrade not see prefix #18129
Unanswered
ArseniyXaoc
asked this question in
Help
Replies: 1 comment
-
During migration if we can't migrate the config file, then we will link it to the CSS file. Can you share a minimal reproduction repo? |
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.
Uh oh!
There was an error while loading. Please reload this page.
-
What version of Tailwind CSS are you using?
v3.4.3
What build tool (or framework if it abstracts the build tool) are you using?
Vite 6.3.1
What version of Node.js are you using?
v20.12.2
What browser are you using?
N/A
What operating system are you using?
macOS
Reproduction URL
A Tailwind Play link or public GitHub repo that includes a minimal reproduction of the bug. Please do not link to your actual project, what we need instead is a minimal reproduction in a fresh project without any unnecessary code. This means it doesn't matter if your real project is private/confidential, since we want a link to a separate, isolated reproduction anyways.
A reproduction is required when filing an issue — any issue opened without a reproduction will be closed and you'll be asked to create a new issue that includes a reproduction. We're a small team and we can't keep up with the volume of issues we receive if we need to reproduce each issue from scratch ourselves.
Describe your issue
After running npx @tailwindcss/upgrade --force the old prefix "apl-" is not transferred to the new tailwind settings and is not updated in the svelte file
Prefix set in tailwind.config.json file:
Also, the link to the config file is not added to style.css via
@config
Beta Was this translation helpful? Give feedback.
All reactions