Skip to content
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

Benefits compared to tsparticles official react lib #170

Closed
RemyMachado opened this issue Mar 24, 2021 · 4 comments
Closed

Benefits compared to tsparticles official react lib #170

RemyMachado opened this issue Mar 24, 2021 · 4 comments
Labels

Comments

@RemyMachado
Copy link

Hello, I couldn't find the answer, so I'll ask :

  • What are the benefits of using this library rather than using react-tsparticles ?

react-tsparticles being the official react package of tsparticles (that react-particles-js is relying on).

Thanks in advance for your response.

@RemyMachado RemyMachado changed the title Benefits compared to tsparticles Benefits compared to tsparticles official react lib Mar 24, 2021
@nobane
Copy link

nobane commented Mar 26, 2021

This project, react-particles-js, uses a typescript wrapper that already provides a react component. Additionally, the version pinned in this project is out of date with the latest typescript wrapper version. That means it has an older version of the core particles library.

I've had issues getting this project to work that seem to be related to it having an old version of tsparticles which in turn means an older version of the core library.

I just switched to the react component in react-tsparticles and it works great. @RemyMachado I recommend to use that, then you only have to worry about that tsparticles staying up-to-date, as opposed to a second layer of dependences by using this project (react-particles-js).

@wufe
Copy link
Owner

wufe commented Mar 26, 2021

I'm indeed planning to deprecate this library in favor of react-tsparticles

@stale
Copy link

stale bot commented Jun 26, 2021

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the stale label Jun 26, 2021
@wufe wufe pinned this issue Jun 29, 2021
@stale stale bot removed the stale label Jun 29, 2021
@stale
Copy link

stale bot commented Apr 16, 2022

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the stale label Apr 16, 2022
@stale stale bot closed this as completed Apr 28, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants