Hysen Labs
Open-source project
supermedium/aframe-watcher avatar
supermedium

aframe-watcher

👀 Companion server for A-Frame Inspector to sync changes back to HTML files.

100 stars25 forksJavaScriptMIT
01
DEEP OPEN-SOURCE ANALYSIS

aframe-watcher: save Inspector edits to your scene files

Editing an A-Frame scene usually means toggling between the editor, the Inspector, and a browser refresh. This companion server removes the refresh by writing Inspector changes straight back into the HTML.

02
DEEP OPEN-SOURCE ANALYSIS

The workflow it kills

The pitch is a question: are you tired of switching back and forth between your text editor, the Inspector, and refreshing? The watcher's answer is that you can now save your changes from the Inspector directly to your HTML files. The Inspector has built-in support with a save button for the Watcher, so the two tools are designed to work as a pair rather than as a manual copy step. aframe-watcher is a companion server, and its whole job is to carry edits from the Inspector back into the project files on disk.

03
DEEP OPEN-SOURCE ANALYSIS

How the save works

There are two small requirements spelled out in the README. Your entities need defined IDs so the watcher knows what to update, and you open the Inspector on an A-Frame scene with ctrl + alt + i, currently on the master or the 0.9.0 version of the Inspector. From there the save button hands the edited state back to the server, which writes it into the scene file.

04
DEEP OPEN-SOURCE ANALYSIS

Why it matters

The value is the removal of the manual transfer step. Previously, visual edits made in the Inspector had to be copied into the source by hand and the page refreshed to see them. The watcher automates that sync, so the file stays in step with what you see in the Inspector. The project is MIT licensed and written in JavaScript, and the homepage points to a page on the supermedium site for context.

06
DEEP OPEN-SOURCE ANALYSIS

Official sources

07
Community notes

Community notes