Skip to content

Conversation

@josecelano
Copy link
Member

Summary

This PR updates npm dependencies and resolves Svelte 5 reactivity warnings across the codebase.

Changes

Dependency Updates

  • Updated 171 packages via npm update
  • Major updates include esbuild, Babel packages, and various @sveltejs packages
  • Security: 36 vulnerabilities remain (primarily in vite-plugin-imagemin dependency chain)

Svelte 5 Reactivity Fixes

Fixed 41 reactivity warnings by properly using $derived() rune for prop-dependent computed values:

  • Updated 9 component files (Button, Cards, RelatedCard, TagCard, BlogPostCard, BlogPreview, CodeBlock, RelatedPostCard, molecule TagCard)
  • Updated 21 blog post pages
  • Refactored blog list page filtering to use reactive patterns
  • Updated contributor layout

Note: One intentional warning remains in Toc.svelte where the selector is intentionally captured at initialization time for the @melt-ui/svelte library.

Testing

  • npm run check passes (0 errors, 1 documented warning)
  • npm run dev runs with clean output
  • ⚠️ Pre-existing build error with /api route (unrelated to these changes)

Additional Notes

See open Snyk PRs (#154, #153, #149, #148, #97) for additional dependency updates that require manual package.json modifications.

- Use $derived for all computed values that depend on props
- Fix Button, Cards, RelatedCard, and TagCard components
- Fix all blog post pages and layouts
- Fix date formatting in BlogPreview, BlogPostCard, etc.
- Fix CodeBlock syntax highlighting reactivity
- Update blog +page to use derived filtering

This eliminates 41 of 42 warnings. The remaining warning in Toc.svelte
is intentional as the selector is passed to a third-party library that
doesn't support dynamic updates.
@josecelano josecelano self-assigned this Dec 21, 2025
@josecelano
Copy link
Member Author

ACK 4170be6

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants