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
Most components now require 'onPointerEnterCapture' and 'onPointerLeaveCapture' #651
Comments
@Deepacks I have the same issue. |
Also, I've tried different versions, but it seems like there is a dependency issue inside Material Tailwind. |
I have the same problem, I hope they solve it soon. |
This is my provisional solution, in the end you should add all the components that come with this problem and redefine the unwanted properties. // material-tailwind.d.ts
import {} from "@material-tailwind/react";
type EventCapture = {
onPointerEnterCapture?: unknown;
onPointerLeaveCapture?: unknown;
};
declare module "@material-tailwind/react" {
export interface ButtonProps extends EventCapture {
placeholder?: unknown;
}
export interface InputProps extends EventCapture {
crossOrigin?: unknown;
}
export interface SelectProps extends EventCapture {
placeholder?: unknown;
}
// more...
} |
@alckordev looks nice. I've decided to use wrappers, but now I'm thinking that your implementation must be easier to maintain. |
@alckordev @phil-situmorang I've managed to solve the issue in a different way. It's as simple as forcing the version of the These are my devDependencies now: {
"devDependencies": {
"@types/node": "20.11.28",
"@types/react": "18.2.65",
"@types/react-dom": "18.2.22",
"autoprefixer": "10.4.18",
"eslint": "8.57.0",
"eslint-config-next": "14.1.3",
"postcss": "8.4.35",
"tailwindcss": "3.4.1",
"typescript": "5.4.2"
}
} |
@Deepacks thank you! |
See the |
@martymh Thank you! It now makes a lot more sense. So, to sort this out, material-tailwind should update its |
I tried opening a PR that bumps the I ran material-tw locally and i saw no warnings or errors. I'll just wait and see if the maintainers accept it. |
Is there any news on this issue I have the same problem? Changing the version of @types/react to 18.2.65 did not work for me unfortunately. Update (Found a workaround): |
Thank you! Works wonders :) |
Hello, this issue started happening today out of the blue.
I did not find anything mentioning it online.
Most components require those two props now, can't manage to fix it.
The typescript warning:
My package.json:
Edit
This happens only when the
@types/react
version is greater than18.2.65
(at this time, latest is18.2.66
)The text was updated successfully, but these errors were encountered: