Update Svelte UX (underlying @layerstack/svelte-stores) to fix inadvertent dark mode removal when rendering a component

[sean-zlai]

Summary

A continuation of an earlier fix, if your system is using dark mode, the class would be removed unintentionally on first render of a Svelte UX component.

This fix occurred in @layerstack/svelte-stores's themeStore and package bumped in latest Svelte UX version. Also bumped LayerChart version which includes a small legend/tooltip click propagation issue (something we wouldn't have encountered yet since we don't use <LineChart ontooltipclick={...}>).

Before

CleanShot.2025-03-06.at.14.52.46.mp4

After

CleanShot.2025-03-06.at.14.57.47.mp4

Checklist

• Added Unit Tests
• Covered by existing CI
• Integration tested
• Documentation update

[coderabbitai]

Walkthrough

This pull request updates dependency versions in the frontend package.json file without altering other configurations. The updates bump the version of the "layerchart" package from ^1.0.5 to ^1.0.6 and the "svelte-ux" package from ^1.0.1 to ^1.0.2.

Changes

File	Change Summary
frontend/package.json	Updated dependency "layerchart" from ^1.0.5 to ^1.0.6 and "svelte-ux" from ^1.0.1 to ^1.0.2.

Possibly related PRs

• Update LayerChart, LayerStack, and Svelte UX packages to 1.0.0 #440: Updates similar dependencies (layerchart and svelte-ux) in the frontend package.
• Update LayerChart to 1.0.3 #460: Involves modifying the "layerchart" dependency in the frontend package.json.
• Update LayerChart to 1.0.1 fixing overlapping high point series highlight and improved LineChart perf (up to 33%) #451: Addresses dependency version updates for "layerchart" in the frontend package configuration.

Suggested reviewers

• ken-zlai

Poem

In code where versions shift anew,
Dependencies rise with changes true.
Layerchart and svelte-ux take flight,
In the package file their stars ignite.
A subtle tune of upgrade bright.

Warning

Review ran into problems

🔥 Problems

GitHub Actions and Pipeline Checks: Resource not accessible by integration - https://docs.github.com/rest/actions/workflow-runs#list-workflow-runs-for-a-repository.

Please grant the required permissions to the CodeRabbit GitHub App under the organization or repository settings.

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro (Legacy)

📥 Commits

Reviewing files that changed from the base of the PR and between f992e7b and bcac5cf.

⛔ Files ignored due to path filters (1)

• frontend/package-lock.json is excluded by !**/package-lock.json

📒 Files selected for processing (1)

• frontend/package.json (1 hunks)

✅ Files skipped from review due to trivial changes (1)

• frontend/package.json

⏰ Context from checks skipped due to timeout of 90000ms (1)

• GitHub Check: enforce_triggered_workflows

---

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.