chore: bump agents-ui package to 6.3.0

[victorgaard]

Why?

• Bumps agents-ui to 6.3.0
• tl;dr what's new:
  • Router capabilities
  • Agent chat
  • Support for different elizaOS versions
  • Bug fixes

https://github.com/fleek-platform/agents-ui/blob/main/CHANGELOG.md (5.0.2 onwards)

Contribution checklist?

• The commit messages are detailed
• The build command runs locally
• Assets or static content are linked and stored in the project
• Document filename is named after the slug
• You've reviewed spelling using a grammar checker
• For documentation, guides or references, you've tested the commands and steps
• You've done enough research before writing

Security checklist?

• Sensitive data has been identified and is being protected properly
• Injection has been prevented (parameterized queries, no eval or system calls)
• The Components are escaping output (to prevent XSS)

References?

Optionally, provide references such as links

Preview?

Optionally, provide the preview url here

[changeset-bot]

⚠️ No Changeset found

Latest commit: 3ac1108

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[angarita-dev]

Okay! Spent quite a bit trying to integrate successfully a post-router version of agents-ui here, but in the end couldn't get around astro limitations for handling SPA behaviour. However in order to prevent blocking new versions of agents-ui I created this PR to expose multiple routing options, with said changes, for this integration we could choose between hash navigation /eliza/#/... or memory navigation /eliza (url-unchanged).

We can continue with the discussion:

• The main blocker is handling the dynamic url paths /agent/:agentId or /drafts/:draftId cannot be expressed using getStaticPaths, see Astro docs on Routing - SSG mode:

  Static (SSG) Mode

  Because all routes must be determined at build time, a dynamic route must export a getStaticPaths() that returns an array of objects with a params property. Each of these objects will generate a corresponding route.

• Rewrites, they seem to enable the use-case we want, however we still don't have a way around the dynamic parameters see Astro docs on Routing - Rewrites

  A rewrite allows you to serve a different route without redirecting the browser to a different page. The browser will show the original address in the URL bar, but will instead display the content of the URL provided to Astro.rewrite().

• Before mentioning splat routes like: /eliza/[...catchAll].astro. Simply won't work without specifying getStaticPaths() check the Astro docs on Errors - getStaticPaths required:

  🚨 Error

  getStaticPaths() function is required for dynamic routes. Make sure that you export a getStaticPaths function from your dynamic route.

---

Relevant discussions around the topic:

• Client-side Routing: This already merged proposal Client-side Routing #532. Moved from Persistent Islands #307 both go over something that a sub-segment of the astro community has always wanted, a SPA mode, which would allow this type of integration.

[heldrida]

Okay! Spent quite a bit trying to integrate successfully a post-router version of agents-ui here, but in the end couldn't get around astro limitations for handling SPA behaviour. However in order to prevent blocking new versions of agents-ui I created this PR to expose multiple routing options, with said changes, for this integration we could choose between hash navigation /eliza/#/... or memory navigation /eliza (url-unchanged).

@angarita-dev Remember this warning I put a few weeks ago https://discord.com/channels/1045027913260617789/1045488357846814771/1347602591743217705

To summarise, I've mentioned that introducing the router will cause build issues in the website, as the build time runs in the node environment and history api's not available.

@angarita-dev you maybe mentioning something else which I'm not noticing at the moment, but what I'll do is to push a few changes here and will update staging. Expect it to work!