-
-
Notifications
You must be signed in to change notification settings - Fork 31
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
switch to the new visjs libraries #314
Comments
Hi @mojoaxel I already the question to another guy from the community. I would glad to contribute it there. I'll drop you an email |
🎉 ngx-vis is now a member of the visjs family! |
One of the first thinks would be to switch to the new visjs libraries. |
Just published version 3.0.0 with the new libraries: https://www.npmjs.com/package/ngx-vis?activeTab=versions We can discuss further steps from there now ;) |
Hi @hypery2k and others!
vis.js has been official declared deprecated. We continue development in the visjs community. There we have two new libraries vis-network and vis-timline and development is progressing fast.
I would highly recommend moving from the old vis dependency to the new libraries. You will find that vis-network now comes with its own typescript bindings and is moving more and more in the direction of typescript.
Also vis-timeline has made a huge leap forward and now includes all features and bug-fixes from timeline-plus and other forks.
I also would like to invite you to collaborate with us in the new visjs community. If you want you could move your fork to the visjs account. You would stay the main maintainer but we could help with reviews and maybe even share some funding 😉
@hypery2k Please contact me is you are interested!
The text was updated successfully, but these errors were encountered: