-
-
Notifications
You must be signed in to change notification settings - Fork 138
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
Typescript issues + Is this actually still alive? #229
Comments
This project is certainly alive and used in production systems such as https://chart-studio.plotly.com/. We do not use TypeScript ourselves, so we don't put any effort into maintaining any kind of TypeScript bindings or integrations or type definitions. The reason the code hasn't changed much is that it's a very stable wrapper around Plotly.js and our production systems have used it as-is for years. We merge community pull requests when they make sense, though, so feel free to contribute any changes you find necessary for your project :) |
Ok, that's what I thought. It is clear now. But still, without typescript, I can't succeed to have it working in a create react app. |
Sounds like fun! |
@nicolaskruchten is it still the case the package is maintained? |
Yes, in fact there's work going on RN in #333 - which should also address the original question in this issue re: TypeScript. |
I faced many issues that are already mentioned on the list of issues. Not to say that I can't have even have the project working with typescript.
My main question here is: is this project actually still alive? No issue seems to have any answer from anybody, since 2 years. And source code is nearly not touched since 2 years as well.
I'm asking this because a component with no community behind is just a no-go for my project.
The text was updated successfully, but these errors were encountered: