chore: update dependencies including major upgrades#189
Merged
josecelano merged 6 commits intodevelopfrom Apr 14, 2026
Merged
Conversation
Bump all non-major-version dependencies to their latest releases: devDependencies: - @eslint/compat: ^2.0.2 -> ^2.0.5 - @sveltejs/kit: ^2.53.1 -> ^2.57.1 - @types/node: ^22.19.11 -> ^22.19.17 - @typescript-eslint/eslint-plugin: ^8.56.1 -> ^8.58.2 - @typescript-eslint/parser: ^8.56.1 -> ^8.58.2 - eslint: ^10.0.2 -> ^10.2.0 - eslint-plugin-svelte: ^3.15.0 -> ^3.17.0 - globals: ^17.3.0 -> ^17.5.0 - mdsvex: ^0.12.6 -> ^0.12.7 - prettier: ^3.8.1 -> ^3.8.2 - prettier-plugin-svelte: ^3.5.0 -> ^3.5.1 - sass: ^1.97.3 -> ^1.99.0 - svelte: ^5.53.3 -> ^5.55.4 - svelte-check: ^4.4.3 -> ^4.4.6 - svelte-eslint-parser: ^1.5.1 -> ^1.6.0 - svelte-sitemap: ^2.7.1 -> ^2.8.0 - tailwindcss: ^4.2.1 -> ^4.2.2 - typescript-eslint: ^8.56.1 -> ^8.58.2 - vite: ^7.3.1 -> ^7.3.2 dependencies: - @tailwindcss/vite: ^4.2.1 -> ^4.2.2 - rehype-pretty-code: ^0.14.1 -> ^0.14.3 The following packages have available major-version updates but are held back due to peer-dependency constraints and will be addressed separately: - @sveltejs/vite-plugin-svelte (6 -> 7, requires vite 8) - vite (7 -> 8) - typescript (5 -> 6) - @types/node (22 -> 25) - svelte-sitemap (2 -> 3)
…rnings The h4 elements are injected by MDsveX markdown rendering at runtime, not present in the static Svelte template, so Svelte's scoped CSS analyser correctly cannot find them. Using :global() mirrors how the existing blockquote rule in the same file is already handled.
- bump vite from ^7.3.2 to ^8.0.8 - bump @sveltejs/vite-plugin-svelte from ^6.2.4 to ^7.0.0 - regenerate lockfile - update dependency upgrade plan progress Validation: - npm run lint - npm run check - npm run build
- bump svelte-sitemap from ^2.8.0 to ^3.1.0 - regenerate lockfile - update dependency upgrade plan progress Validation: - npm run lint - npm run check - npm run build
- bump typescript from ^5.9.3 to ^6.0.2 - bump @types/node from ^22.19.17 to ^25.6.0 - regenerate lockfile - update dependency upgrade plan progress Validation: - npm run lint - npm run check - npm run build
Member
Author
|
ACK c66a436 |
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.
Summary
This PR updates project dependencies and completes the planned major-version upgrades in a stacked sequence, submitted as a single PR from the top branch.
Included updates
Validation
All checks pass with 0 errors and 0 warnings.
Notes