Charles KWON OhJun
b19bb0c445
When fnode is invoked from a cwd outside fivenode_go (e.g. a sibling
project like /Users/.../solmade), the legacy fallback
"../../fivedev/five" was resolved against the caller's cwd, pointing
fnode at /Users/fivedev/five which doesn't exist. go mod tidy then
failed with "open /Users/fivedev/five/go.mod: no such file".
New resolution order in fiveRoot():
1. walkUpForModule("five") — same as before, wins inside the
Five source tree.
2. fiveFromFnodeGoMod() — parse the `replace five => <path>`
line in fivenode_go's own go.mod (found via fnodeRoot()),
resolving relative paths against that root.
3. Hardcoded relative fallback (legacy).
Lets sibling apps run `fnode build app/foo.prg ...` from their own
directory without needing to cd into fivenode_go first.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
fivenode_go
FiveNode for Five — a Harbour-compatible web framework that compiles to a single Go binary. No Node.js, no FFI, no Apache. PRG sources go in, one executable comes out.
Successor to the koffi/N-API based fivenode framework, rebuilt on the Five Pure-Go runtime.
Status
Early bootstrap — Phase 1a in progress.
Architecture
Browser ──── HTTP/HTTPS ──── fivenode_go single binary
├─ Five hbrt VM (PRG interpreter / compiled)
├─ Five hbrtl (483 standard RTL functions)
├─ hbrtl_ext/httpserver — HTTP server RTL
├─ hbrtl_ext/capi — bridge_*.prg helpers
├─ hbrtl_ext/pgrtl — PostgreSQL client RTL
├─ app/ — bridge_*.prg + app PRG
└─ go:embed — static assets
fnode build api/*.prg --extra-rtl=hbrtl_ext/... -o myapp produces a
self-contained binary. No external dependencies beyond what the app code
itself opens (e.g. a Postgres connection).
Build
go build -o fnode ./cmd/fnode
./fnode build app/hello.prg -o hello
./hello
License
Copyright (c) 2026 Charles KWON OhJun. All rights reserved.