-
-
Notifications
You must be signed in to change notification settings - Fork 326
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 'crossOrigin' is missing in type <Input /> ??? #427
Comments
I have the same issue with several components now :(. Updates: |
Having same issue with all components too |
I am having the same issue as well. I can set InputProps => React.ComponentProps<'input'> => IntrinsicElements => GlobalIntrinsicElements => JSX.IntrinsicElements I find this property: {
//...
crossOrigin?: CrossOrigin;
// ...
} where type CrossOrigin = 'anonymous' | 'use-credentials' | '' | undefined; So I am not sure why my editor is inferring the type as |
I got the same error and also thought, it's because of this package. But actually the error occurs, when I update With |
Can confirm I had this issue a while ago and the above solution fixed it |
It still happens in |
Has anyone found a solution to this but with Geist? (https://github.com/geist-org/geist-ui) |
I only had to update typescript to 5.2.2, React to 18.2.0, and @types/react to 18.2.21. |
i update |
Do we have any progress on this issue? I'd like to suggest that specifying |
I have the same problem, but no solved for me this solution.
|
This is actually a bug in |
I have the simililar problem |
someone solve this ? |
To solve this, I just changed the @types/react to 18.2.19 and the issue is gone My other packages:
|
any updates? |
The latest versions have a bug, see creativetimofficial/material-tailwind#427 for more.
Downgrading |
Thanks friend, this even solved the component problems that require a placeHolders for me. Update the @react-types. and I have "@material-tailwind/react": "2.1.8". |
it still not fixed in latest @types/react & @material-tailwind/react isn't it? |
It's not with "@material-tailwind/react": "2.1.9" and "@types/react": "18.2.73" i've locked down @types/react to 18.2.9 for now. |
* 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]>
Having to use old @types/react doesn't seem a good solution i believe, i get other problems when using older version of that package, any news? Optional props should be optional, I am preferring to add crossOrigin="undefined" as of now instead of using older version of @types/react |
me funciono cambiar este el type a esta version |
What is this?
This happens on the last release "@material-tailwind/react": "^2.1.0"
The text was updated successfully, but these errors were encountered: