Skip to content

Add line breaks before/after code blocks #291

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Jul 25, 2025
Merged

Add line breaks before/after code blocks #291

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 6 additions & 0 deletions component-model/src/design/why-component-model.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -22,12 +22,15 @@ binary `.wasm` file.

A core module usually corresponds to a single binary `.wasm` file.
Here's what the `file` command outputs for a sample `.wasm` file:

```console
$ file adder.wasm
adder.wasm: WebAssembly (wasm) binary module version 0x1 (MVP)
```

The file can also be inspected
using [the `wasm-tools` CLI](https://github.com/bytecodealliance/wasm-tools):

```console
$ wasm-tools print adder.wasm | head -1
(module
Expand Down Expand Up @@ -151,12 +154,15 @@ Conceptually, a component is a WebAssembly binary
that is restricted to interact
only through the modules' imported and exported functions.
Components use a different binary format:

```console
$ file add.component.wasm
add.component.wasm: WebAssembly (wasm) binary module version 0x1000d
```

Inspecting the file with the `wasm-tools` CLI
shows more clearly that it contains a component:

```
$ wasm-tools print add.component.wasm | head -1
(component
Expand Down