chore(deps-dev): bump vite from 5.4.21 to 8.0.10 in /use-cases/game-of-throne-demo/frontend in the npm_and_yarn group across 1 directory

[dependabot]

Bumps the npm_and_yarn group with 1 update in the /use-cases/game-of-throne-demo/frontend directory: vite.

Updates vite from 5.4.21 to 8.0.10

Release notes

Sourced from vite's releases.

v8.0.10

Please refer to CHANGELOG.md for details.

v8.0.9

Please refer to CHANGELOG.md for details.

v8.0.8

Please refer to CHANGELOG.md for details.

v8.0.7

Please refer to CHANGELOG.md for details.

v8.0.6

Please refer to CHANGELOG.md for details.

v8.0.5

Please refer to CHANGELOG.md for details.

v8.0.4

Please refer to CHANGELOG.md for details.

create-vite@8.0.3

Please refer to CHANGELOG.md for details.

v8.0.3

Please refer to CHANGELOG.md for details.

create-vite@8.0.2

Please refer to CHANGELOG.md for details.

v8.0.2

Please refer to CHANGELOG.md for details.

create-vite@8.0.1

Please refer to CHANGELOG.md for details.

v8.0.1

Please refer to CHANGELOG.md for details.

plugin-legacy@8.0.1

Please refer to CHANGELOG.md for details.

create-vite@8.0.0

Please refer to CHANGELOG.md for details.

plugin-legacy@8.0.0

Please refer to CHANGELOG.md for details.

v8.0.0

Please refer to CHANGELOG.md for details.

... (truncated)

Changelog

Sourced from vite's changelog.

8.0.10 (2026-04-23)

Features

• update rolldown to 1.0.0-rc.17 (#22299) (a4d06d9)

Bug Fixes

• hmrClient.logger.debug and hmrClient.logger.error looked different from other HMR logs (#22147) (a4d828f)
• css: show filename in CSS minification warnings for .css?inline (#22292) (83f0a78)
• optimizer: allow user transform.target to override default in optimizeDeps (#22273) (5c7cec6)
• remove format sniffing module resolution from JS resolver (#22297) (b8a21cc)

Code Refactoring

• enable some typecheck rules (#22278) (9437518)
• typecheck client directory (#22284) (40a0847)

8.0.9 (2026-04-20)

Features

• update rolldown to 1.0.0-rc.16 (#22248) (2947edd)

Bug Fixes

• allow binding when strictPort is set but wildcard port is in use (#22150) (dfc8aa5)
• build: emptyOutDir should happen for watch rebuilds (#22207) (ee52267)
• bundled-dev: reject requests to HMR patch files in non potentially trustworthy origins (#22269) (868f141)
• css: use unique key for cssEntriesMap to prevent same-basename collision (#22039) (374bb5d)
• deps: update all non-major dependencies (#22219) (4cd0d67)
• deps: update all non-major dependencies (#22268) (c28e9c1)
• detect Deno workspace root (fix #22237) (#22238) (1b793c0)
• dev: handle errors in watchChange hook (#22188) (fc08bda)
• optimizer: handle more chars that will be sanitized (#22208) (3f24533)
• skip fallback sourcemap generation for ?raw imports (#22148) (3ec9cda)

Documentation

• align the descriptions in READMEs (#22231) (44c42b9)
• fix reuses wording in dev environment comment (#22173) (9163412)
• fix wording in sass error comment (#22214) (bc5c6a7)
• update build CLI defaults (#22261) (605bb97)

Miscellaneous Chores

• deps: update dependency dotenv-expand to v13 (#22271) (0a3887d)

8.0.8 (2026-04-09)

Features

• update rolldown to 1.0.0-rc.15 (#22201) (6baf587)

... (truncated)

Commits

• 32c2978 release: v8.0.10
• a4d06d9 feat: update rolldown to 1.0.0-rc.17 (#22299)
• a4d828f fix: hmrClient.logger.debug and hmrClient.logger.error looked different f...
• 83f0a78 fix(css): show filename in CSS minification warnings for .css?inline (#22292)
• b8a21cc fix: remove format sniffing module resolution from JS resolver (#22297)
• 40a0847 refactor: typecheck client directory (#22284)
• 5c7cec6 fix(optimizer): allow user transform.target to override default in optimizeDe...
• 9437518 refactor: enable some typecheck rules (#22278)
• ce729f5 release: v8.0.9
• 605bb97 docs: update build CLI defaults (#22261)
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
• @dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
• @dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
• @dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
• @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions
  You can disable automated security fix PRs for this repo from the Security Alerts page.

[codecapyai]

CodeCapy Review ₍ᐢ•(ܫ)•ᐢ₎

• PR: chore(deps-dev): bump vite from 5.4.21 to 8.0.10 in /use-cases/game-of-throne-demo/frontend in the npm_and_yarn group across 1 directory #1
• Commit: f5d25b0

Codebase Summary

The repository contains EverOS, a multi-use platform including several use cases. The Game of Thrones demo in use-cases/game-of-throne-demo/frontend is a web application that showcases an interactive Q&A experience with the themes from 'A Game of Thrones'. This frontend is built using Vite and bundled assets to deliver a smooth interactive experience.

PR Changes

This pull request updates the Vite dev dependency from version 5.4.21 to 8.0.10 in the Game of Thrones demo frontend. This version bump can impact the development server’s hot module replacement (HMR), asset bundling, and error overlays. The changes need to be verified on user-facing UI components to ensure that interactive elements and page load behaviors remain consistent.

Setup Instructions

1. Install Node.js and npm if not already installed on your system.
2. Install the pnpm CLI globally using the command: sudo npm install -g pnpm
3. Clone the repository: git clone <repository_url>
4. Navigate into the repository directory: cd EverOS
5. Navigate into the Game of Thrones demo frontend folder: cd use-cases/game-of-throne-demo/frontend
6. Install dependencies by running: pnpm install
7. Start the development server by running: pnpm dev
8. Open your preferred browser and navigate to the localhost URL indicated by the development server (commonly http://localhost:3000) to begin testing.

Generated Test Cases

1: Frontend Build and Initial Load Test ❗️❗️❗️

Description: Verifies that the Game of Thrones demo frontend builds correctly and loads the main UI without runtime errors. This ensures that the Vite update does not break the initial page render or asset loading.

Prerequisites:

• Have Node.js, npm, and pnpm installed
• Fresh clone of the repository

Steps:

1. Open a terminal and install the pnpm CLI globally if not already installed (sudo npm install -g pnpm).
2. Navigate to the repository root and then into the use-cases/game-of-throne-demo/frontend directory.
3. Run 'pnpm install' to install dependencies.
4. Run 'pnpm dev' to start the Vite development server.
5. Open a web browser and navigate to the indicated localhost URL (usually http://localhost:3000).
6. Observe the initial page load and ensure that the Game of Thrones themed demo UI is rendered, including any expected titles, images, and interactive sections.

Expected Result: The web application loads successfully with all assets rendered correctly without any JavaScript errors. The main layout, text, and images should display as intended.

2: Hot Module Replacement (HMR) Functionality Test ❗️❗️❗️

Description: Checks that the development server's hot module replacement works as expected after the Vite version bump. It verifies that changes in the source code are reflected immediately in the browser.

Prerequisites:

• Frontend dev server running from the previous test

Steps:

1. Open the code editor and locate a simple UI component (for example, a header or title in index.html or a corresponding component file).
2. Modify some text content (e.g., change a header title) and save the file.
3. Observe the browser to see if the updated text appears without a full page reload.
4. Check that no error overlays or unexpected behavior occur during HMR.

Expected Result: The changes are reflected instantly in the browser via HMR without a full page reload. There are no runtime errors or broken UI elements following the update.

3: Error Overlay Display Test ❗️❗️

Description: Ensures that when a runtime error occurs in the frontend code, Vite's error overlay displays an informative error message to the user. This test confirms that updated error handling in Vite 8.0.10 works as expected.

Prerequisites:

• Frontend dev server running

Steps:

1. Open a UI component file and deliberately introduce a syntax error (for example, remove a closing bracket in a JavaScript module).
2. Save the file and observe the browser.
3. Verify that Vite displays an error overlay indicating the location and nature of the error.
4. Fix the error after verification to restore normal operation.

Expected Result: An error overlay appears on the browser screen, clearly indicating the error details (file and error message) without crashing the entire dev server. Once corrected, the overlay should disappear and the UI should update normally.

4: Static Asset Loading Test ❗️❗️

Description: Verifies that static assets such as images, CSS styles, and other resources load correctly under the updated Vite configuration. This ensures visual consistency and proper asset bundling.

Prerequisites:

• Frontend dev server running

Steps:

1. Open the web application in the browser.
2. Inspect different sections of the UI to confirm images, fonts, and CSS styles load correctly.
3. Use the browser developer tools to check the Network tab for any missing assets or 404 errors.
4. Interact with UI elements that rely on CSS or images to verify they render and behave as expected.

Expected Result: All static assets are loaded without errors. Visual elements such as images and fonts should render properly, and no broken resource links are present.

Raw Changes Analyzed

File: use-cases/game-of-throne-demo/frontend/package.json
Changes:
@@ -25,6 +25,6 @@
     "eslint-plugin-react-hooks": "^4.6.0",
     "eslint-plugin-react-refresh": "^0.4.5",
     "typescript": "^5.3.3",
-    "vite": "^5.0.8"
+    "vite": "^8.0.10"
   }
 }

[codecapyai]

🚀 Launching Scrapybara desktop...

[codecapyai]

❌ Something went wrong:

status_code: 500, body: {'detail': 'Error creating instance: HTTPSConnectionPool(host=\'dd71ce9e4c14175cfb2d4b4d613159f4.sk1.us-west-1.eks.amazonaws.com\', port=443): Max retries exceeded with url: /api/v1/namespaces/scrapybara-instances/services (Caused by NameResolutionError("<urllib3.connection.HTTPSConnection object at 0x7f04a2387bd0>: Failed to resolve \'dd71ce9e4c14175cfb2d4b4d613159f4.sk1.us-west-1.eks.amazonaws.com\' ([Errno -2] Name or service not known)"))'}

[Fearvox]

Triage note (2026-05-13): This is a 2-week-old Dependabot PR bumping vite in the game-of-throne-demo frontend. The demo is community-supported (not covered by security SLA per SECURITY.md).

Recommendation: review for breaking changes (v5→v8 is a major jump) and either merge if clean or close if the demo's pinned vite version is intentional.