-
-
Notifications
You must be signed in to change notification settings - Fork 328
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
Property 'placeholder' is missing in type... for some 'non-form' components? #528
Comments
It's also in |
Same problem on all Typography, List, Accordion etc |
If it's not a feature, it' a bug. Strange enough, installing back I did today an update of VC on Mac too. Could it be related to the VisualCode update? I'm not fluent in VC and don't know how to downgrade to test. By the way. I had and still have a similar issue with the Input component. It requires So, if your project is still in the beginning and small, one could temporary work around with adding |
@don-esteban this not related to VC. 😞 Try to run This bug is happening with I made some regression tests, and on But, on 2.1.0-react version, the bug came back to It's my first time on |
This is a bug, introduced in The "placeholder" issue is likely related. It was introduced in TL;DR: Until this is fixed, your best bet is to downgrade Hope this helps :) |
I downgraded Now, all things are working. Thanks, Bob! ❤️ |
@rafaelvieiras You are right Not sure how to address this, except pinning the version of @types/react. Thx! |
Updated material-tailwind today 2.1.7 and types for latest versions to fix a specific SSR render in Next 14 and face this problem with almost every component from the lib... I confirm too that, the only way I found to deal with this was backing version to "@types/react": "18.2.42" ... I won't touch this anymore since the application will grow and we don't have time to waste ... Thx @BobDotCom !!! 🤘 |
Sorry to open this up again but to me it seems like the issue revolves around |
I had could solve my problem changing version like Bob mentions, some like this:
|
I had to go down to 18.2.19 to fix this. 18.2.42 didnt solve it. // package.json
|
I did the following to fix the bug of material-tailwind. |
Confirm I was using Type problem was with Button component and some others |
this solve my problem |
But having a minor version instead of the major is not a problem? We can have type errors if we continue using that old version. Am I wrong? |
Certainly, it is, and I'm not aware of any other tools allowing a bug of this nature to linger for such an extended period without even informing the community about future plans. We've decided to move away. Currently, we utilize Material Tailwind exclusively for quick and dirty prototyping. |
Still throwing a bunch of errors after trying all the different versions of material/tailwind and types/react. Is there a specific typescript version dependency? |
|
How did this help, I have installed react 18 and tried to upgrade it with 'npm i react-update', but in my package.json react keeps showing 18. |
Set your app to run react 17 if your other dependencies allows react 17. If not then kindly step away. I ended up running bootstrap for my project. To much of a hassle to fix my dependencies for v17. |
is this not solved yet? |
I was already using daisyUI in my project. I wanted to speed up development by switching to Material Tailwind. But, I'll stick to daisyUI moving forward. Yes, it's not the same but stable and flexible. Also easy to pick up IMO. |
Type '{ children: Element[]; }' is missing the following properties from type 'Pick<CarouselProps, "children" | "className" | "color" | "transition" | "translate" | "slot" | "style" | "title" | "onChange" | "loop" | "onClick" | "key" | "defaultChecked" | ... 252 more ... | "slideRef">': placeholder, onPointerEnterCapture, onPointerLeaveCapturets(2739) I also had the same error. I was using material-tailwind library with next.js 14. <Carousel I added this attribute now it's not showing any typescript error. |
I downgrade @types/react to v18.2.42 and it works! |
Hi, I'm having the same issues, but downgrade @types/react to v18.2.42 DID NOT work for me! I generated new create-react-app project with typescript, material-tailwind and tailwind css just to be sure. |
Looks like there's a bug with recent version of react/types, that causes valid Typescript to fail with some React components. This was failing builds with my install stepper UI changes. Pinning to the last working version, as recommended in the github issue that's tracking the bug, appears to have solved the problem for me. creativetimofficial/material-tailwind#528
Looks like there's a bug with recent version of react/types, that causes valid Typescript to fail with some React components. This was failing builds with my install stepper UI changes. Pinning to the last working version, as recommended in the github issue that's tracking the bug, appears to have solved the problem for me. creativetimofficial/material-tailwind#528
Looks like there's a bug with recent version of @types/react, that causes valid Typescript to fail with some React components. This was failing builds with my install stepper UI changes. Pinning to the last working version, as recommended in the github issue , appears to have solved the problem for me. creativetimofficial/material-tailwind#528
Looks like there's a bug with recent version of @types/react, that causes valid Typescript to fail with some React components. This was failing builds with my install stepper UI changes. Pinning to the last working version, as recommended in the github issue , appears to have solved the problem for me. creativetimofficial/material-tailwind#528
* feat: render input groups Render input groups as form fieldsets. Doesn't look great, though. Going to take a pass at a better UX. * feat: add Accordion component and use for input groups If you have a lot of inputs, having groups can help organize them on the screen, but it also pads the list out and makes them even longer. This PR adds an Accordion component, then uses it to display the groups. The customer can view one group at a time (or open them all if they want to.) * feat: install material tailwind Mainly to use their stepper component. * feat: basic install stepper ui * feat: update and reprovision if install has been created * feat: basic install status view * feat: layout and styles * refactor: clean up file organization * fix: pin to last working version of react/types Looks like there's a bug with recent version of @types/react, that causes valid Typescript to fail with some React components. This was failing builds with my install stepper UI changes. Pinning to the last working version, as recommended in the github issue , appears to have solved the problem for me. creativetimofficial/material-tailwind#528 * fix: typescript build errors * feat: add component redeploy step to install update * fix: more readable form field spacing * fix: handle null input groups * fix: stop throwing errors With the error message component set up, we can return all errors and display them to the user. * refactor: remove console logs * refactor: decompose stepper into smaller components * feat: poll less often 10 seconds should more frequent enough * refactor: group install status components together * fix: install button loading state correct layout * feat: can close error messages * fix: use correct card component for company step * fix: add missing iterator key * fix: type errors
I don't think anyone needs to downgrade
|
* feat(home): completed Home page * Genres list (#10) * profile-page * GenresList Complete * rework GenresList * fix(home): genre list --------- Co-authored-by: shifinmalik <[email protected]> Co-authored-by: Muhammed-Rahif <[email protected]> * fix(getting-started): carousel replaced with material-tailwind * fix(material-tailwind): version types issue creativetimofficial/material-tailwind#528 creativetimofficial/material-tailwind#427 * fix: file change from js/jsx to ts/tsx * fix(home): header carousel * fix(home): ui * fix(home): ui update --------- Co-authored-by: shifinmalik <[email protected]> Co-authored-by: shifinmalik <[email protected]> Co-authored-by: Muhammed-Rahif <[email protected]>
Where does this piece of code go? |
Looks like Input still doesn't work even with this @types/react version. |
create a file inside the src folder called I'm also new in react tailwind so feel free to correct me. |
Usually just put it in the root directory, since another .d.ts file - next-env.d.ts is also there. |
"dependencies": { in vite-env.d.ts file /// fixed ! thanks |
I configured it as below. but, still not working.... is wrong...? plz help me.. node v20.11.0
|
I encountered the same issue when I tried using @vitejs/plugin-react-swc. If you replace it with @vitejs/plugin-react, the issue will go away. However, considering this issue, as well as the type problems and the slow response from the developer, it seems that using @material-tailwind/react right now is not the best idea. |
@M34R7 thx your reply. you gave me a great answer.. thank you 👍 |
|
My old solution of pinning types/react to 18.2.19 isn't the best. Better to update to the new version, and use a patch of code to fix the broken parts. For reference, see creativetimofficial/material-tailwind#528
My old solution of pinning types/react to 18.2.19 isn't the best. Better to update to the new version, and use a patch of code to fix the broken parts. For reference, see creativetimofficial/material-tailwind#528
* build(deps): update to next.js 15 with codemod * chore: reconfigure eslint * fix: fix eslint issues * fix: temporary fix for types/react My old solution of pinning types/react to 18.2.19 isn't the best. Better to update to the new version, and use a patch of code to fix the broken parts. For reference, see creativetimofficial/material-tailwind#528 * Revert "chore: reconfigure eslint" This reverts commit 2aaf4c1. * Revert "fix: fix eslint issues" This reverts commit eab9d7f. * Revert "fix: temporary fix for types/react" This reverts commit d3ebe02.
I encountered the same issue where @types/react version 18.2.42 caused compatibility problems with certain components, especially Input. To fix this, I downgraded to version 18.2.19, which resolved the issue for now. However, this is more of a temporary solution, and the root cause should be investigated for a proper fix. // package.json "devDependencies": { |
hi folks, I'm currently having a weird issue with the material-tailwind library, I tried to use the Sticky NavBar, and I got the following weird error:
btw, this happen with the Button, Typography, Navbar and IconButton (idk if other components will have the issue)
I've used this library in another project and that error never appeared, I have more dependencies but this are the ones I believe may be related:
here is an image of my code:
let me know if you need more info to figure it out, btw I get rid of the error by simply adding
placeholder=""
to all the components with the error, but checking the documentation the propplaceholder
doesn't exists for those componentsThe text was updated successfully, but these errors were encountered: