-
Notifications
You must be signed in to change notification settings - Fork 86
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
some warnings come from tailwind #122
Comments
i assume you have a |
i import it without customize config file just use directly |
i found the warnings was introduced in tailwindlabs/tailwindcss#7065 that seems we need to modify the config with add content key in create method |
I'm getting this issue even with the "content" prop in my tailwind.config.js. Here's what it looks like: |
any solution yet? |
I'm away from my office for a while, without my normal computer and with really poor internet, but I think I know what might be causing these warnings, and I cooked up a quick beta release to test my theory. Could one or more of you give it a test and report back? To install, run: npm install twrnc@next @chinieer @LivingInLimbo @Klin-Coders |
has solved! thank you for all you did |
@chinieer thanks for reporting back. just released |
Do I have to change my package.json if I installed the beta release? Fixed the warnings for me as well. |
warn - The |
What version of twrnc are you on? You shouldn’t have that error if you’re on the latest.
…Sent from my iPhone
On Feb 8, 2022, at 2:11 PM, amit kumar saraswat ***@***.***> wrote:
warn - The content option in your Tailwind CSS configuration is missing or empty.
warn - Configure your content sources or your generated CSS will be missing styles.
warn - https://tailwindcss.com/docs/content-configuration
tailwindcss": "^3.0.19
plz somebody help
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you modified the open/close state.
|
@jaredh159 , same here |
@aacassandra what version of |
tailwind CSS version: 3.0.18
tailwind-react-native-classname version: 3.0.1
it seems a tailwind bug but has solved in tailwindlabs/tailwindcss#7210 , but it still happens in tailwind-react-native-classname
The text was updated successfully, but these errors were encountered: