chore(deps): catch up next, motion, lucide-react and types - #46
Merged
Merged
Conversation
- next + eslint-config-next 16.3.3 -> 16.3.4, kept in lockstep - motion 13.1.1 -> 13.2.0, lucide-react 1.38.0 -> 1.40.0 - @types/node 26.4.1, @types/react-dom 19.2.7 - hero glb + effect chain re-probed, motion ssr output intact
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
This branch was successfully deployed
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.
sweeps what
npm outdatedwas still flagging after the two security fixes (#43 fflate, #44 browserslist).nextandeslint-config-next16.3.3 -> 16.3.4, kept in lockstepmotion13.1.1 -> 13.2.0lucide-react1.38.0 -> 1.40.0@types/node26.4.1,@types/react-dom19.2.7the last four were already in range, so only the two pinned next packages moved in
package.json.since motion moved and it drives the scroll reveals, plus three/postprocessing are in the same tree: re-probed the hero effect chain (
BrightnessContrast,Bloom,Vignette, combinedEffectPass) and parsed the actual.glb(2 meshes, 2 materials, bbox intact). motion's ssr output still rendersopacity:0+translateY(18px)on/about, and the resume previews still resolve to v5.typecheck,lint,buildgreen on node 22,npm audit0, all 7 routes 200.remaining
npm outdatedrows are the two deliberate holds (eslint10,typescript7), both still blocked upstream.