Use tsparticles v3 for fireworks #2259
Draft
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
With tsparticles v3 and a background mask, I was able to get fireworks show up above images and text inputs while avoiding tsparticles/tsparticles#4870. I tried the background mask in our v2 version but it didn't work as expected.
I let the fireworks preset configure most because I couldn't just copy the config since it now requires the engine as an argument for the color utils. I compared our options with the preset and I believe I applied our customization to the preset.
However, I can still see fireworks going off-screen on small sizes, so I am not sure if 573dd06 worked or just wasn't applied here for some reason.
I need to go now, will check later.
Not sure how long we want to keep the fireworks though?
Video
2025-07-04.17-01-25.mp4
Checklist
Are your changes backward compatible? Please answer below:
yes
For example, a change is not backward compatible if you removed a GraphQL field or dropped a database column.
5
. Fireworks are now above images and text inputs but still go off-screen on small sizes though.For frontend changes: Tested on mobile, light and dark mode? Please answer below:
yes
Did you introduce any new environment variables? If so, call them out explicitly here:
no