Doug A

Thanks @jsoverson (especially for choosing Svelte & Vite over React 😂). I just need enough to get started and check this out in the browser. I'll give it a shot...

While I'm here, can you confirm if the LLM Llama example also is running 100% on the browser client too?

Ran into the first issue: `build.rs` won't build: `cargo build` **unknown field `operations`** ```sh error: failed to run custom build command for `jinja v0.1.0` Caused by: process didn't exit successfully:...

Found [`just`](https://github.com/casey/just#installation), will make a PR to add a line to the docs

Even when using `just build` I still get ``` Error: Could not parse manifest /home/doug/code/rust/components/jinja/component.wick as YAML: unknown field `operations`, expected one of `name` , `metadata`, `package`, `host`, `resources`, `import`,...

Looks like the `operations` block needs to be indented one more level to `just build`. Pull request sent.

> be really great is a full-stack `rust-libp2p` example where we have a server & a client, possibly reusing a common codebase and deploying them in the browser and as...

@RangerMauve Can we name change his thread to **Advertise Dat and Archive version updates on the network** - [ ] Expected behavior: Update an archive version in `Dat-Js`, see the...

More testing this morning, discovery issue #8 still exists between a new `Dat-JS` and a listening `dat-node`. Create a new Dat with `Dat-JS` and try to replicate the archive in...

Hmm, ok @RangerMauve thanks. I would have thought that the moe `dat-gateway` would be able to connect to the `dat-node` with no issue? Awww, NATs. Any workaround suggestions? Maybe something...