Skip to content

Conversation

@HighPriest
Copy link

@HighPriest HighPriest commented Aug 9, 2025

Hi @osousa
I wanted to iterate on your creation for some time now and I finally got to re-writing the front-end application, matching it to standards of Svelte 5.

There are still quite a few things to do, so here is a WIP to bring attention to things happening.

TODO:

  • Contribute to svelte-standalone project
  • Re-organize commit history, into individual features
  • Include build scripts for different types of anchoring
    • Anchoring to
    • Anchoring to
      (User defined container)
      • Allow user to adjust positioning of the UI
      • Allow user to adjust scaling of the UI
  • Fix some styling
    • Fix minimum-height
    • Make the session form more appealing
      • Add a greeting with more information, what the user has just clicked into
      • Fit the styling to rest of the application
    • Verify that the styles are correctly decoupled from the rest of the site
      • Make sure the fonts and their sizing are correct
    • Configurable branding
      • Configurable logo
      • Configurable Username
  • On chat creation, make the session information passed by the user, be sent to the bot as a message

Extra features:

  • Close UI with ESC
  • Notifications worker for new messages
  • Make a smooth transition between bubble and chatbox view
  • Call to action animated speech bubble. Pointing that the Chat box is available.
    • Make it run on mount
    • Make it run on long interval

@osousa
Copy link
Contributor

osousa commented Aug 25, 2025

Hello @HighPriest ,

this is awesome 😎 , thank you so much for the contribution, and i'm sorry for the late reply, i was on vacations. Will take a look at your PR today and merge it tomorrow for sure.

Once again thank you very much for contributing!

@HighPriest
Copy link
Author

Please wait for me to finish noted maintenance. I might be able to do it today, or I'll finish it aln tomorrow.

Big thanks to @brenoliradev for figuring out how to make reliable standalone builds of Svelte 5

@HighPriest
Copy link
Author

@osousa
I think I am done here.
There are still issues with the Svelte Standalone project, but I have put in a few workarounds into this project and marked them in TODO.md to take appropriate actions, when time comes.

@HighPriest HighPriest changed the title WIP: Svelte5 upgrade Svelte5 upgrade Aug 27, 2025
@brenoliradev
Copy link

Hey - I think you don't need to worry with your TODO --production flag since you're using css on .svelte.

Svelte actually purges all unused css by default so you should be fine =)

Let me know how it goes.

@HighPriest
Copy link
Author

HighPriest commented Aug 28, 2025

Hey @brenoliradev
Svelte-stanvalone is currently removing ALL CSS from the project, if used with "--production" flag. My latest contributions kept this "bug" kind of by design, to encourage us, to find a way to keep the "purge css" plugin and have it not wipe all styles completely, from SvelteKit projects.

I've just tested this PR on mobile and here are bugs that are still in the code:

  • Some messages get lost
    • I've had first messages, sent either way, not arriving at all
    • Re-openning a closed session, does not load messages from the server. User has to have browser window open to receive messages.
  • The window is still WAY too short by default
    • I remember vividly, fixing the height issue. Got to look into this again.
  • The notification icon is not visible
    • I think I broke it, when playing with the bubble size
    • Would be nice to actually add the "notifications worker" to the app. Shouldn't be much work and would make the app much more functional.
  • Installation readme does not emphasise that Config file is mandatory for the app to work

Mind that I am using Cromite in incognito mode for these tests. But using a browser with most permissions disabled by default, shouldn't break the app.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants