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

some warnings come from tailwind #122

Closed
chinieer opened this issue Feb 1, 2022 · 13 comments · Fixed by #127
Closed

some warnings come from tailwind #122

chinieer opened this issue Feb 1, 2022 · 13 comments · Fixed by #127

Comments

@chinieer
Copy link
Contributor

chinieer commented Feb 1, 2022

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
image

@jaredh159
Copy link
Owner

i assume you have a content prop in your tailwind config?

@chinieer
Copy link
Contributor Author

chinieer commented Feb 1, 2022

i assume you have a content prop in your tailwind config?

i import it without customize config file just use directly

@chinieer
Copy link
Contributor Author

chinieer commented Feb 3, 2022

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

@LivingInLimbo
Copy link

I'm getting this issue even with the "content" prop in my tailwind.config.js. Here's what it looks like:
module.exports = { content: ["./pages/**/*.{html,ts}", "./components/**/*.{html,ts}"], theme: { extend: {}, }, plugins: [], };

@1finedev
Copy link

1finedev commented Feb 5, 2022

any solution yet?

@jaredh159
Copy link
Owner

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

@chinieer
Copy link
Contributor Author

chinieer commented Feb 6, 2022

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

@jaredh159
Copy link
Owner

@chinieer thanks for reporting back. just released 3.0.2 which contains the fix.

@LivingInLimbo
Copy link

Do I have to change my package.json if I installed the beta release? Fixed the warnings for me as well.

@amitkrsrswt
Copy link

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

@jaredh159
Copy link
Owner

jaredh159 commented Feb 8, 2022 via email

@aacassandra
Copy link

@jaredh159 , same here
im using tailwind 3.0.24

@jaredh159
Copy link
Owner

@aacassandra what version of twrnc (not tailwindcss) are you running?

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

Successfully merging a pull request may close this issue.

6 participants