John Miller

It's been about two years and apparently this PR works just fine. Why is this not being merged?

!important should not be necessary. This is very awkard and clunky design. It also makes it impossible to use css libraries like Tailwind with React-Tooltip.

> I agree. Please submit a PR if you are able to fix it! > […](#) > On Tue, Sep 14, 2021 at 9:11 PM John Miller ***@***.***> wrote: !important...

> The fix above posted by @zackypick worked for me, but transitioning all properties did give a similar bug as described by @karashiiro. I am doing some custom positioning so...

This bug is replicating in my own project as well. Changing the displayName to match the export name kills the error.

> Please be more considerate to open source maintainers, who are often doing this work for free in their spare time. The "+1" spam doesn't help. If this feature matters...

> Quill's `text-change` API distinguishes between programmatic and user-initiated changes, and React-Quill sends that information with the new HTML content in the onChange callback. > > Have you looked into...

Me, when my 2MB image can't be fetched because the max content size is 4MB 

If this is importing using `import * as kmeans from 'ml-kmeans'`, then you need to document it

The fact that critical types are not exposed is a red flag for this library. The necessary work that needs to be done is to go through the whole library...