🏡 0.6.6 Rooms as app spaces

All the previous experiments were just a play and now we got a bit more serious. Now everything in the app will be situated inside a SEA pair space. It'll have certificates for everyone to use in all accepted use cases. The root app room is hard-coded and is a starting point of the room network exploration. This opens many interesting use cases and makes data management much more reliable.

All the room navigation is working now, spaces are now working inside rooms - the coordinates are stored inside, not in the user graph. Certified writes are bigger and a bit slower, but it's another level of app credibility and encapsulation.

✨✨✨ Stability +10

Got the space really reactive to guests coming and going. With links and profile pages.

Feeds got updated too! The icons and covers are stored separately at a content-addressed nodes, but you can still download full zips of posts and feeds as well as upload them back easily.

Better UI with more stable ui-layer component for managing overlays and routes too.

Youtube video overview of the release

The same video on Joystream

💾 Upload and download zip files with posts

Now we got all the tools to export any Gun graph data not only to plain MD files, but to zip files with images inserted into the nodes. It'll be easy to add any file type handling and so we will be able to download and upload whole media projects with pdfs, mp3s and more.

👀 New site with docs for all the layers

Vitepress generates all the docs. Thinking of automating the documentation as much as I can – so then it's easier to keep everything up to date.

✨ First fully usable component kit.

Finally I got all the pieces working and you can just import the components (along with styles) into your vue project and have them working just fine!

Now we have a small vitepress site to demonstrate the use of these components in a SSR environment. I still struggle for it not to run Gun at component import - so we need a small wrapper for client-side dynamic imports, but it's rather ok – these components don't need to be server rendered any way.

Have fun playing with @gun-vue! We're open for any contributions.

Relay server is a proper ES module

With Node versions > 12 we can get rid of the require and exports and use plain ESM syntax. So here we have it!

@gun-vue ecosystem of 4 workspaces

Now we have a whole ecosystem going on here!

https://www.npmjs.com/settings/gun-vue/packages

@gun-vue organization now distributes composable functions, vue components and the relay server to everyone @ npmjs.com. The setup is quite starightforward and is a good foundation for deeper development.

🧚🏽‍♀️ Pulse and players

The server puts it's own timestamp as a pulse to the game graph and it's the major tool to monitor the connection to the GUN relay. And also any visitor can join the game and get a floating avatar, whose position is synced across all visitors. The scale of the avatar is determined by the 'age' – the difference between the player's pulse timestamp and current client time.

The system is set up to build rather big apps with Gun and Vue with Vite as a bundler - the p2p synced game engine is just 65 kiB gzipped! Very nice start!