chore: update demo app deps

[BCsabaEngine]

Summary by CodeRabbit

• New Features

  • Introduced a bug fix that prevents error code generation issues related to '@' signs in file names, improving character handling for filenames.

• Bug Fixes

  • Resolved an error that occurred when '@' was included in file names, enhancing overall application functionality.

• Chores

  • Updated various development dependencies to their latest versions for improved performance and security.

[coderabbitai]

Walkthrough

The pull request introduces updates across multiple files, primarily focusing on enhancing character handling in filenames and updating various development dependencies. A new section in the CHANGELOG.md details a bug fix for an error related to the '@' sign in filenames. Additionally, several packages in the package.json files have been upgraded to their latest versions, reflecting ongoing maintenance efforts.

Changes

File	Change Summary
CHANGELOG.md	Added section for version 1.5.1, documenting a bug fix for '@' sign in filenames.
demo/svelte/package.json	Updated multiple devDependencies to newer versions, including @rollup/plugin-swc and svelte.
package.json	Updated @types/node and eslint versions to newer releases.
src/index.ts	Modified regex for filename processing to include more special characters for sanitization.

Possibly related PRs

• feat: support PsychicHttp v2 #29: Updates in CHANGELOG.md for version 1.5.0 related to PsychicHttp v2, which may involve similar character handling improvements.

Tip

New features

Walkthrough comment now includes:

• Possibly related PRs: A list of potentially related PRs to help you recall past context.
• Suggested labels: CodeRabbit can now suggest labels by learning from your past PRs. You can also provide custom labeling instructions in the UI or configuration file.

Notes:

• Please share any feedback in the discussion post on our Discord.
• Possibly related PRs, automatic label suggestions based on past PRs, learnings, and possibly related issues require data opt-in (enabled by default).

---

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

Share

• X
• Mastodon
• Reddit
• LinkedIn

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>.
  • 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 generate interesting stats about this repository and render them as a table.
  • @coderabbitai show all the console.log statements in this repository.
  • @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.

[coderabbitai]

Actionable comments posted: 0

Outside diff range, codebase verification and nitpick comments (1)

src/index.ts (1)

38-38: Updated regex for filename processing

The updated regex [!&()+./@{}~-] is correctly formatted to include the new characters as intended. This change should ensure that filenames with these characters are processed without errors, aligning with the bug fix noted in the CHANGELOG.md.

However, consider adding a comment above this line to explain why these specific characters are being replaced, which could help future maintainers understand the context of this change.

Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between d7cd023 and 554b4a3.

Files ignored due to path filters (6)

• demo/svelte/dist/assets/index-Bq8Tite1.js is excluded by !**/dist/**
• demo/svelte/dist/assets/index-lzaGR1AU.js is excluded by !**/dist/**
• demo/svelte/dist/favicon.png.gz is excluded by !**/dist/**, !**/*.gz
• demo/svelte/dist/index.html is excluded by !**/dist/**
• demo/svelte/package-lock.json is excluded by !**/package-lock.json
• package-lock.json is excluded by !**/package-lock.json

Files selected for processing (4)

• CHANGELOG.md (1 hunks)
• demo/svelte/package.json (1 hunks)
• package.json (1 hunks)
• src/index.ts (1 hunks)

Files skipped from review due to trivial changes (2)

• demo/svelte/package.json
• package.json

Additional comments not posted (1)

CHANGELOG.md (1)

5-7: Review of CHANGELOG.md updates

The addition of version 1.5.1 and the description of the bug fix are clear and well-documented. The explanation of the characters now protected (!&()+./@{}~-) is specific, which is good for transparency and understanding the scope of the bug fix.