Repository navigation
v0.6.0
WASI decoupling: Wavelet no longer special-cases any WASI interface. The
compiler vendors no WASI WIT and has no built-in wasi:cli/wasi:http
knowledge; a component declares the host interfaces it imports and exports
explicitly, and their WIT is fetched into the project by wkg. These are
breaking changes.
Added
wkgandwacare now runtime dependencies ofwavelet build/wavelet new.wkg(the WebAssembly package tooling) fetches host WIT, andwac
(the WebAssembly composition tool) composes components. Both must be on
PATH(the Homebrew formula declares them; orcargo install wkg wac-cli).
The interpreter (wavelet run) andcargo testdo not need them.- Project layout with a
wit/directory. A project now carries its WIT
package and fetched dependencies on disk:wit/holds the synthesized world,
wit/deps/holds the host/dependency WIT thatwkgfetched, andwkg.lock
pins the dependency versions.wavelet newscaffoldswit/and runswkg wit fetchto populatewit/deps/and writewkg.lock. wavelet buildnow composes into a single artifact. It generates a
.wacdescribing how the project's components wire together and runswac composeto produce one composedout/app.wasm, with host (wasi:*) imports
left unsatisfied for the runtime to provide.wavelet composeremains as the
manual/explicit alternative.- Output and arguments now go through explicitly-imported WASI interfaces.
A program that wants stdout/args importswasi:cli/stdout,
wasi:cli/environment, andwasi:io/streams(as ordinaryImportforms)
and drives them through the generic canonical-ABI bridge, exactly as the
httptemplate importswasi:http/types+wasi:io/streams. The cli
template was migrated to this shape. - The generic canonical-ABI bridge now lowers/lifts every non-resource WIT
value kind and resource handles/methods/drop driven by a parsed WIT
signature, so an arbitrary host or third-party interface can be imported and
exported without compiler-side special-casing.
Removed
- The
Targetspecial form is gone. A file no longer adopts a host world
withTarget "wasi:cli/command"; instead it exports that world's interface
directly, e.g.Export {iface: "wasi:cli/run" name: run result: result}.
A source file usingTargetnow fails to read. - The
print,println,args,read-line, andenvbuiltins are gone.
There is no built-in I/O path; output and argument access happen by importing
and calling the relevant WASI interfaces (see Added).wavelet run
interprets pure cross-component logic only and produces no program output. - The vendored WASI WIT (
src/wasi-http.wit) and all the hand-coded WASI
magic (thehttp/*intrinsics, thewasi:cli/commandtarget translation,
the forcedwasi:io/streamsimport) were removed; host WIT now comes from
wit/deps.
Full Changelog: v0.5.0...v0.6.0