chore(deps): @tsparticles 4 (major) - #82
Open
lacymorrow wants to merge 1 commit into
Open
lacymorrow wants to merge 1 commit into
lacymorrow wants to merge 1 commit into
Conversation
- @tsparticles/engine 3.9.1 -> 4.4.0
- @tsparticles/slim 3.9.1 -> 4.4.0
- @tsparticles/react 3.0.0 -> 4.4.0 (requires engine 4.4.0 exactly)
Breaking changes handled in src/components/ui/sparkles.tsx (the only consumer):
- @tsparticles/react 4 removed initParticlesEngine in favour of
<ParticlesProvider init>; the init callback must be a stable reference, so it
now lives at module scope and the provider replaces the useState/useEffect gate
- particles.color / particles.stroke / shape.fill moved under particles.paint
({ color, fill, stroke }); the old keys were silently ignored in v4
- effect.fill, move.attract and move.trail were removed from the option types
(all were disabled or empty here) and are dropped
sparkles.tsx is tsc-excluded (src/components/ui/**) so it was type-checked in
isolation against the v4 types and is clean. It is only imported by cover.tsx,
which no route renders, so this needs a visual check before merge.
Claude-Session: https://claude.ai/code/session_01KLWmWU1KLE2diUH14ryqv1
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
One sentence
Major bump of the three
@tsparticles/*packages from 3 to 4 withsparkles.tsxmigrated to the v4 API (left open for review because it is a major with source changes).Bumps
Breaking changes and what changed
Sources: engine CHANGELOG (https://github.com/tsparticles/tsparticles/blob/main/engine/CHANGELOG.md), paint docs (https://github.com/tsparticles/tsparticles/blob/main/markdown/Options/Particles/Paint.md), and the shipped
@tsparticles/react@4.4.0type declarations.@tsparticles/react4 removedinitParticlesEngine. The wrapper now exportsParticlesProvider(takes a stableinit(engine)callback and renders children once loaded) anduseParticlesProvider.sparkles.tsxmoves theloadSliminit to a module-scopeinitEngineand wraps<Particles>in<ParticlesProvider init={initEngine}>, replacing the olduseState/useEffectgate.particles.paint = { color, fill, stroke };particles.color,particles.strokeandshape.fillare no longer read (particles would silently render default white). The component now setspaint.color.valuefromparticleColor,paint.fill.enable: true,paint.stroke.width: 0.effect.fill,move.attractandmove.trailno longer exist in the v4 option types; all three were disabled or empty here and are removed.@tsparticles/react@4.4.0pins@tsparticles/engine4.4.0 exactly, so the three packages move in lockstep.sparkles.tsxistsc-excluded (src/components/ui/**), so it was type-checked in isolation against the 4.4.0 types and is clean. It is only imported bycover.tsx, which no route renders, so a visual check of the particle effect is still needed before merging.Verification
pnpm typecheckcleanpnpm test: 4 files, 16 tests greenpnpm exec vitest run --config vitest.config.node.ts: 3 files, 21 tests greenpnpm buildpassesnext startsmoke:/200,/changelog200,/changelog/nope-xyz404,/faq200,/nope-404404Installed with
--ignore-scripts(isolated-vm postinstall fails under Node 26 locally; matches how Vercel builds).https://claude.ai/code/session_01KLWmWU1KLE2diUH14ryqv1