.ts/.js from compiled Forst. You can use one, two, or all three.
The three paths and how they connect:
Pick your path
forst generate emits TypeScript stubs, but the invoke wire protocol is JSON over HTTP. Any Node runtime works — Express, Remix, plain node. Examples use .ts because that is what the generator outputs.Caveats
Node interop paths are at different maturity levels. Read the caveats on the page that matches your path.- Generated types are structural only. No runtime constraint rules in
.d.ts. Generate client types § Caveats - Invoke from Node (dev server, built-in HTTP server,
@forst/sidecar,@forst/client) is experimental. Call Forst from Node § Caveats - Call legacy JavaScript from Forst (
import node,forst/nodert) is experimental and may require Node in the deploy image. Call JavaScript from Forst § Caveats
Related
Mix with Go packages
Forst compiles to Go — import stdlib and third-party packages.
Dev server
forst dev HTTP contract for local iteration.