ActiveState allows you to update your Svelte application state easily and in real-time from your Rails backend. Its a combination of npm package and ruby gem, that gives you an application-wide Svelte 5 $state object, and methods to manipulate this state object using dot-notation.
With ActiveState you have an application-wide state object like this:
<script>
import { State } from 'activestate'
</script>
<h1>{State.projects[projectId].name}</h1>and you can update it in real-time from your Rails backend like this:
ProjectChannel[project].state("projects", project.id, "name").set("My awesome project")Let's assume you have a web app and would like to display real-time messages to a specific user. This can be easily done with ActiveState by pushing new messages to a centralized state object as they happen. Let's have a look:
First, we of course need a channel that we can subscribe to:
# user_channel.rb
class UserChannel < ApplicationCable::Channel
def subscribed
stream_for current_user
end
endThen, inside your component, set up a subscription and iterate over state.messages.
<script>
import { subscribe, State } from 'activestate'
import { onDestroy } from 'svelte'
// Set up a subscription to the UserChannel
const unsubscribe = subscribe('UserChannel', {user_id: something})
// Don't forget to unsubscribe when the component is destroyed
onDestroy(unsubscribe)
// Iinitialize it with an empty array
State.messages ||= []
const messages = $derived(State.messages)
</script>
{#each messages as message}
<p>{message.text}</p>
{/each}Now you can server-side push directly into State.messages through the UserChannel:
# Somewhere in your Ruby code:
UserChannel[some_user].state('messages').push({id: 4, text: "Hello from Ruby"})And update the message:
UserChannel[some_user].state('messages').upsert({id: 4, text: "Changed text"})All state mutations operate on a path. This path can be either specified via dot-notation (eg projects.421.name), or as an array (eg. ["projects", project.id, "name"]).
ActiveState comes with 4 built-in mutators: set, assign, upsert, and delete (by the way, when did people start to say "mutating"):
UserChannel[some_user].state('current_user.name').set("John")Replaces the value of current_user.name with John.
UserChannel[some_user].state('current_user').assign({name: 'new name'})Uses Object.assign to merge the passed object onto current_user.
UserChannel[some_user].state('current_user.notices').upsert([{id: 4, name: "new name"}])This iterates over the array in current_user.notices, and performs an upsert using specified key
If called on an array, it iterates over the array and deletes all entries who's keys match the provided object.
If called on an object, it deletes they provided key on the object
You can also call functions that "natively" exist on objects in the state. For example, if you have an array in current_user.notices, you can call its native push function:
UserChannel[some_user].state('current_user.notices').push "next chunk"You can also define custom methods to mutate your state.
import { registerMutator, State } from 'activestate'
registerMutator('append', function(currentValue, data) {
return currentValue.concat(data)
})
<p>
Here is a very long string: {State.long_string}
</p>UserChannel[some_user].state('long_string').append "next chunk"The state method is also available on a Channel instance. That means that you can update Svelte stores through a specific connection, instead of broadcasting to all subscribers:
# user_channel.rb
class UserChannel < ApplicationCable::Channel
def subscribed
stream_for current_user
state('current_user').set(current_user.as_json)
end
endWhen using ActiveState in an SSR context, the server-side javascript process is usually shared between requests. Therefore it is of importance to call reset() before or after rendering, to clear the state and avoid any data leakage between requests.
import { reset } from 'activestate'
reset()
// ... rest of code comes hereWasn't sure at first, but now I think it's awesome. Svelte 5 introduced fine-grained reactivity for objects declared with $state. That means that even if your object becomes huge with deeply nested data, it should not have any impact on performance. So, yeah, I think it's clever and smart 🤓
Add this line to your application's Gemfile:
gem 'activestate'And then execute:
$ bundle install
Install the package:
$ npm i -D activestate