Sync with core e578904

[ludeeus]

No description provided.

[coderabbitai]

Walkthrough

Walkthrough

In this update, we've made some nifty enhancements to the project, streamlining the browser compatibility criteria in the .browserslistrc, updating various dependencies in package.json, and aligning the homeassistant-frontend with the latest commit for improved functionality. Think of it as giving your project a fresh haircut and a new outfit—looking sharp and ready to tackle the web!

Changes

File(s)	Change Summary
.browserslistrc	Refined modern build criteria to target browsers from the last year and those in alpha/beta; added service worker support for legacy builds.
homeassistant-frontend	Updated subproject commit identifier to the latest version, reflecting current enhancements and bug fixes.
package.json	Updated multiple dependencies to their latest versions for improved security and features; added browserslist-useragent-regexp for better compatibility; specified a patch for workbox-build.

Sequence Diagram(s)

sequenceDiagram
    participant User
    participant Frontend
    participant Backend

    User->>Frontend: Requests page
    Frontend->>Backend: Fetches data
    Backend-->>Frontend: Returns data
    Frontend-->>User: Displays page

Loading

Here’s a quick look at how the user interacts with the frontend and backend! Just like sending a message in a bottle, but way faster and without the chance of getting it caught in a storm.

---

Recent review details

Configuration used: CodeRabbit UI
Review profile: ASSERTIVE

Commits

Files that changed from the base of the PR and between eed6d9f and 7f6fc33.

Files ignored due to path filters (1)

• yarn.lock is excluded by !**/yarn.lock, !**/*.lock

Files selected for processing (3)

• .browserslistrc (2 hunks)
• homeassistant-frontend (1 hunks)
• package.json (5 hunks)

Additional comments not posted (7)

homeassistant-frontend (1)

1-1: Verify the subproject commit update.

The subproject commit has been updated to e578904ff7a1b0d7a0940cd5a0fb58ce64f10e21. Ensure that this commit is valid and brings in the desired updates.

Verification successful

Alright, let's play detective and find out what's going on with this elusive commit! 🕵️‍♂️ Let's check if the commit exists locally and take a peek at the submodule configuration.

---

Looks like our commit is playing hide and seek! 🕵️‍♀️ Let's list the recent commits in the homeassistant-frontend submodule to find the right one.

---

The commit e578904ff7a1b0d7a0940cd5a0fb58ce64f10e21 is valid and exists in the submodule homeassistant-frontend. 🕵️‍♂️

• The commit e578904 is part of the recent commit 7f6fc33 in the submodule.

Looks like our commit was just playing hard to get! Everything checks out. 🎉

Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Description: Verify the subproject commit update.

# Test: Fetch the commit details. Expect: Commit exists and is valid.
git fetch origin
git show e578904ff7a1b0d7a0940cd5a0fb58ce64f10e21

Length of output: 242

---

Script:

#!/bin/bash
# Description: Verify the subproject commit update.

# Check if the commit exists in the local repository.
git cat-file -t e578904ff7a1b0d7a0940cd5a0fb58ce64f10e21

# Inspect the submodule configuration to understand the expected state.
git config --file .gitmodules --get-regexp path

Length of output: 341

---

Script:

#!/bin/bash
# Description: List recent commits in the submodule to find the correct commit.

# Navigate to the submodule directory.
cd homeassistant-frontend

# List recent commits in the submodule.
git log --oneline -n 10

Length of output: 123

.browserslistrc (3)

2-14: Streamlined modern browser criteria—looking sharp!

The criteria for modern builds have been refined to target recent browsers, exclude unmaintained ones, and require support for dynamic imports of ES modules. This should help in minimizing transpilation and polyfills.

---

Line range hint 22-36:
Legacy browser support—keeping the oldies but goodies!

The criteria for legacy builds now ensure support for browsers released in the last seven years with a minimum global utilization of 0.05%. This helps in maintaining compatibility with older browsers while leveraging modern web technologies.

---

38-42: New section for legacy browsers with service workers—nice touch!

The [legacy-sw] section mirrors the legacy criteria but adds a requirement for service worker support. This enhances the capability of legacy builds to leverage modern web technologies.

package.json (3)

Line range hint 25-107:
Dependency updates—keeping things fresh and secure!

Multiple dependencies have been updated to their latest versions. This helps in ensuring compatibility, security, and access to new features. Make sure to run your tests to verify compatibility.

---

61-61: New dependency added—browserslist-useragent-regexp!

The new dependency browserslist-useragent-regexp has been added with version 4.1.3. This suggests an enhancement in browser compatibility handling. Ensure that its usage is well-integrated and tested.

---

114-114: Custom patch applied—workbox-build!

The workbox-build dependency has been specified with a patch reference. Ensure that this patch is necessary and does not introduce any issues.

---

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:

‼️ IMPORTANT
Auto-reply has been disabled for this repository in the CodeRabbit settings. The CodeRabbit bot will not respond to your replies unless it is explicitly tagged.

• 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 as 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.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

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.