chore(deps): update dependency eslint-plugin-svelte to v3.13.0

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
eslint-plugin-svelte (source)	3.12.5 -> 3.13.0

---

Release Notes

sveltejs/eslint-plugin-svelte (eslint-plugin-svelte)

v3.13.0

Compare Source

Minor Changes

• #​1323 074af20 Thanks @​marekdedic! - feat(no-navigation-without-resolve): checking link shorthand attributes

Patch Changes

• #​1388 005e9fd Thanks @​marekdedic! - fix(no-navigation-without-resolve): allowing undefined and null in link hrefs

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[claude]

Pull Request Review: Update eslint-plugin-svelte to v3.13.0

Summary

This PR updates eslint-plugin-svelte from 3.12.5 to 3.13.0 in the frontend dependencies. This is an automated dependency update generated by Renovate bot.

Code Quality & Best Practices ✅

Positive aspects:

• Clean, automated dependency update with proper semantic versioning
• Changes are isolated to lockfiles (package-lock.json and yarn.lock), indicating no breaking changes requiring code modifications
• The update follows the project's dependency management practices

Dependency Analysis

What's new in v3.13.0:
Based on the PR description, this release includes:

Minor Changes:

• Enhancement to no-navigation-without-resolve rule: now checks link shorthand attributes (#1323)

Patch Changes:

• Fix for no-navigation-without-resolve rule: now properly allows undefined and null in link hrefs (#1388)

Potential Issues & Considerations ⚠️

1. Dual Package Managers: The PR updates both package-lock.json (npm) and yarn.lock (Yarn). This suggests the project might be using both package managers, which can lead to:

   • Inconsistencies between lock files
   • Confusion for contributors about which package manager to use
   • Potential version drift between the two lock files

   Recommendation: Consider standardizing on a single package manager (either npm or Yarn) for consistency.

2. Registry URL Changes: Some dependencies in yarn.lock show registry URL changes (switching between registry.yarnpkg.com and registry.npmjs.org). While this is generally harmless, it's worth monitoring.

3. New ESLint Rule Behavior: The enhanced no-navigation-without-resolve rule now checks link shorthand attributes. If your codebase uses these patterns, you may see new ESLint warnings/errors after this update.

Security Concerns 🔒

Low Risk:

• This is a devDependency update for a linting tool (not production code)
• No known security vulnerabilities are mentioned in the release notes
• The changes are from a reputable source (Svelte official eslint plugin)
• Minor version bump suggests backward compatibility

Performance Considerations 📊

No Performance Impact:

• ESLint plugins only run during development and CI/CD
• No runtime performance implications for production code
• The changes are rule enhancements, not performance-related

Test Coverage 🧪

Considerations:

• Since this is a linting tool update, no application tests are directly affected
• The updated rules might flag new linting issues in existing code
• Recommendation: Run the full linting suite after merging to identify any new warnings:

  cd frontend && npm run lint
  # or
  cd frontend && yarn lint

Merge Recommendation ✅

APPROVED with minor suggestions

This is a safe, low-risk dependency update that:

• ✅ Brings improved ESLint rules for better code quality
• ✅ Includes bug fixes for existing rules
• ✅ Has no breaking changes
• ✅ Follows semantic versioning correctly
• ✅ Is isolated to development dependencies

Action Items Before/After Merge:

1. Run linting checks to ensure no new warnings are introduced
2. Consider addressing the dual package manager setup (npm + Yarn)
3. Verify CI/CD passes all checks

Follows repository conventions:

• ✅ Uses conventional commit format: chore(deps): ...
• ✅ Automated update keeps dependencies current
• ✅ No manual code changes required

Great job keeping dependencies up to date! 🚀

---

Review generated with assistance from Claude Code

[claude]

Pull Request Review - eslint-plugin-svelte v3.13.0 Update

Summary

This PR updates eslint-plugin-svelte from v3.12.5 to v3.13.0 via Renovate bot. This is a minor version update that includes both new features and bug fixes.

---

Code Quality & Best Practices ✅

Positive aspects:

• Automated dependency update following best practices
• Lock files (both package-lock.json and yarn.lock) are properly updated
• Version constraint in package.json remains flexible (^3), allowing future patch updates
• Changes are limited to dependency manifests only - no code changes required

Notes:

• The package.json specifies "eslint-plugin-svelte": "^3" which correctly allows this minor update
• Both npm and yarn lock files are present - consider standardizing on one package manager to avoid potential inconsistencies

---

Changes Overview

According to the release notes, this version includes:

New Features:

• Enhanced no-navigation-without-resolve rule to check link shorthand attributes (#1323)
  • This will provide better linting for SvelteKit navigation patterns

Bug Fixes:

• Fixed no-navigation-without-resolve to properly allow undefined and null in link hrefs (#1388)
  • This resolves false positives in the linting rules

---

Potential Issues & Considerations ⚠️

1. Stricter Linting Rules: The new feature may flag additional navigation patterns in your Svelte components. Based on the repo structure, you have 21 .svelte files that could be affected by the enhanced no-navigation-without-resolve rule.

2. Testing Recommendation:

   • Run npm run lint (or yarn lint) in the frontend directory to ensure no new linting errors are introduced
   • The rule specifically affects link navigation, so components with <a> tags or SvelteKit navigation should be checked

3. Lock File Considerations:

   • Both package-lock.json and yarn.lock are updated, suggesting dual package manager support
   • Consider documenting which package manager should be used for development to maintain consistency

---

Security Concerns 🔒

No security concerns identified:

• This is an official release from the sveltejs organization
• The update comes from Renovate bot, which is properly configured
• No dependencies with known vulnerabilities are introduced
• The integrity hashes in lock files are properly updated

---

Test Coverage 📋

Current state:

• This is a dev dependency update that affects linting only
• No runtime code changes are required
• The existing test suite should remain unaffected

Recommendations:

1. Verify CI pipeline passes (linting step specifically)
2. Run npm run lint locally to catch any new linting warnings/errors
3. If new linting issues are found, they should be addressed before merging

---

Performance Considerations ⚡

No performance impact:

• Dev dependency only (not included in production bundles)
• May have negligible impact on linting speed during development
• Lock file changes optimize dependency resolution

---

Recommendation

✅ APPROVE with minor action items:

This is a safe dependency update that brings useful improvements to the linting rules. The changes are well-tested by the upstream maintainers.

Before merging:

1. Ensure CI passes (especially linting checks)
2. Run npm run lint or yarn lint in the frontend directory
3. Address any new linting warnings if they appear (the enhanced no-navigation-without-resolve rule may catch previously undetected issues)
4. Consider documenting your preferred package manager (npm vs yarn) in the README or contributing guidelines

Merge confidence: High - This is a minor version bump from a well-maintained eslint plugin with a clear changelog and no breaking changes.

---

Review conducted following conventional commits and the repository's development guidelines.