git404hub

what is dilemma fr?

madoshakalaka/dilemma — explained in plain English

Analysis updated 2026-07-18 · repo last pushed 2026-04-27

RustAudience · developerComplexity · 4/5MaintainedSetup · moderate

tl;dr

A working full-stack Rust demo app that exposes a real problem: rust-analyzer can't properly check code shared between a WebAssembly frontend and a server backend at the same time.

vibe map

mindmap
  root((repo))
    What it does
      Demonstrates editor problem
      Full stack Rust app
      Shared entity crate
    Tech stack
      Rust
      WebAssembly
      Tokio
    The problem
      rust-analyzer picks one target
      Frontend or backend breaks
      No single correct view
    Audience
      Full stack Rust developers
      rust-analyzer contributors
    Workaround
      Compile halves separately
      Switch editor settings

Code map

Detail Auto

An interactive map of this repo's files and how they connect — its source is parsed live in your browser. Click Visualize to build it.

filefunction / class

what do people make with this?

VIBE 1

See a concrete reproduction of the rust-analyzer dual-target analysis problem in a real full-stack app.

VIBE 2

Understand why shared crates compiled differently for WebAssembly and server targets confuse code editors.

VIBE 3

Use it as a reference case when discussing or contributing a fix to rust-analyzer's workspace analysis.

VIBE 4

Learn how a Rust project splits a shared entity crate between browser and server-optimized data structures.

what's the stack?

RustWebAssemblyTokio

how it stacks up fr

madoshakalaka/dilemma0xr10t/pulsefi404-agent/codes-miner
Stars00
LanguageRustRustRust
Last pushed2026-04-27
MaintenanceMaintained
Setup difficultymoderatehardmoderate
Complexity4/54/53/5
Audiencedeveloperdeveloperdeveloper

Figures from each repo's GitHub metadata at analysis time.

how do i run it?

Difficulty · moderate time til it works · 30min

Requires compiling the frontend for WebAssembly and the backend for the server separately since rust-analyzer can't check both at once.

prompts (copy fr)

prompt 1
Clone dilemma and show me exactly which files cause rust-analyzer to show false errors on the frontend versus backend.
prompt 2
Explain why the entity crate in dilemma exports different types for WebAssembly versus the server target.
prompt 3
What would it take for rust-analyzer to analyze dilemma's frontend and backend against their correct targets simultaneously?
prompt 4
Help me set up separate compile commands for dilemma's frontend and backend so I avoid the editor error confusion.

Frequently asked questions

what is dilemma fr?

A working full-stack Rust demo app that exposes a real problem: rust-analyzer can't properly check code shared between a WebAssembly frontend and a server backend at the same time.

What language is dilemma written in?

Mainly Rust. The stack also includes Rust, WebAssembly, Tokio.

Is dilemma actively maintained?

Maintained — commit in last 6 months (last push 2026-04-27).

How hard is dilemma to set up?

Setup difficulty is rated moderate, with roughly 30min to a first successful run.

Who is dilemma for?

Mainly developer.

peek the repo → explain another one

This repo across BitVibe Labs

double-check against the repo, no cap.