Open Viraj-10 opened 2 weeks ago
I also followed the guide and the button didn't display. Has this problem been resolved?
Seeing the same issue. Fresh expo react native app with no changes and follow the gluestack-ui guide both using CLI and manually and styles don't display.
I am experiencing the same issue in my Next.js project and also try to applying Tailwind utility classes to the button, there is no effect on its style.
Hey @mithun-si , @JackGrantham @gaofc, Can you please share repo? and also which OS you are using windows
or mac
?
I'm using Windows
I'm using Windows too.
https://codesandbox.io/p/devbox/playaround-hpfszq
this is the my code sandbox link I think that you can get idea from there and also for your information I am using next.js and npx gluestack-ui@latest init npx gluestack-ui@latest add --all command to install gluestack-ui and it's components
I'm seeing the same issue in an Expo project. The components work but no styling is applied.
Hey everyone! We've released an updated version of the CLI with bug fixes to address the reported issues. Let us know if you face any issues while using it.
Hi @vaibhk20, I am created fresh Next.js project and then install the latest gluestack-ui with this command "npx gluestack-ui@latest init" and try to used Button component but still the style is not applied
Next.js version: 14.2.16
Hey @mithun-si, Please add "jsxImportSource": "nativewind"
to your tsconfig
file.
I am still seeing the same issue.
Here are the steps I am taking:
I also have tried adding "jsxImportSource": "nativewind" to my tsconfig file and this did not change anything for me.
I am using Windows 11
Here is my code: https://github.com/JackGrantham/gluestackv2-test
Hey @JackGrantham, I have created a PR with all the fixes. Seems like cli is not working properly on windows.
Yeah thanks. I got it working by copying over the configs from the starter kit app.
Thanks @Viraj-10 your changes worked. However, I did need to downgrade to Node v20 from v22 since I was running into issues with 'require' not being defined in some imports in tailwind.config.js and metro.config.js
Does this also work with nativewind 4.1.23?
Hey @Viraj-10 , After adding this "jsxImportSource": "nativewind" to mytsconfig file now I can use tailwindcss it's work thanks but the default behavior still not working for example
<Button size="md" variant="outline" action="primary" >
<ButtonText>Hello World!</ButtonText>
</Button>
it should show a button with some outline right? but my case I only see the Hello World! text nothing else
Next.js: 14.2.16 windows: 11 pro
Does this also work with nativewind 4.1.23?
@mathis-kdio, We are releasing support for v4.1 this week.
Hey @Viraj-10 , After adding this "jsxImportSource": "nativewind" to mytsconfig file now I can use tailwindcss it's work thanks but the default behavior still not working for example
<Button size="md" variant="outline" action="primary" > <ButtonText>Hello World!</ButtonText> </Button>
it should show a button with some outline right? but my case I only see the Hello World! text nothing else
Next.js: 14.2.16 windows: 11 pro
@mithun-si please check your content property in tailwind.config.js
file. give proper path to all the components and pages. checkout guide from tailwind here
Hey @Viraj-10 , After adding this "jsxImportSource": "nativewind" to mytsconfig file now I can use tailwindcss it's work thanks but the default behavior still not working for example
<Button size="md" variant="outline" action="primary" > <ButtonText>Hello World!</ButtonText> </Button>
it should show a button with some outline right? but my case I only see the Hello World! text nothing else Next.js: 14.2.16 windows: 11 pro
@mithun-si please check your content property in
tailwind.config.js
file. give proper path to all the components and pages. checkout guide from tailwind here
Thanks @Viraj-10 it's working now but for action="primary"/"secondary" the color is not shown why? is there anything else need to add to show color I am using gluestack-ui CLI also when I am building my Next.js application there is a lot's of type related warning and error and that's why application build is failed please solve this ASAP and If I use //@ts-ignore for where need type I can successfully build application so if I use //@ts-ignore is there any problem arise in future?
@Viraj-10 Any updates on when #2475 will be released? Nativewind 4.1 supposedly addresses https://github.com/nativewind/nativewind/issues/924, which has been a major hassle for both production and development.
Discussed in https://github.com/gluestack/gluestack-ui/discussions/2526