prettier

Author: GabrielaReyna

sites/browserpod/src/content/docs/00-overview.mdx

@@ -33,9 +33,10 @@ import { DISCORD_URL } from "@/consts.ts";
 Instead of provisioning a cloud server, BrowserPod's API enables a client browser to host full runtimes compiled to WebAssembly (Wasm), running at native speed.
 
 <div class="m-4 flex justify-center">
-	[Get started](/docs/getting-started/quickstart) · [Basic Tutorial](/docs/getting-started/expressjs) · [API reference](/docs/reference) · [GitHub
-	repository](https://github.com/leaningtech/browserpod-meta)
-	· [Licensing](/docs/more/licensing)
+	[Get started](/docs/getting-started/quickstart) · [Basic
+	Tutorial](/docs/getting-started/expressjs) · [API reference](/docs/reference)
+	· [GitHub repository](https://github.com/leaningtech/browserpod-meta) ·
+	[Licensing](/docs/more/licensing)
 </div>
 
 BrowserPod is ephemeral by design. Each **pod** (_see [pod](/docs/more/glossary#pod)_) runs inside a browser tab and ends when the tab closes or reloads. Because BrowserPod runs inside the browser, each Pod is constrained by the browser’s security model, isolated from the user’s OS, with limited access (via syscalls) to local files or system resources unless you explicitly provide it.
@@ -64,8 +65,6 @@ Everything runs client‑side within the browser sandbox, so users don’t need
 - **Security**: The BrowserPod API boots instances in the browser's sandbox, inheriting its security.
 - **Cost**: Because BrowserPod runs instances in the browser, it comes at a fraction of the cost of cloud sandboxes, with a generous free tier.
 
-
-
 ## How it works (high level)
 
 - BrowserPod ships a build of Node.js that targets CheerpOS (a runtime that provides a Linux‑like syscall interface to Wasm).
@@ -79,7 +78,6 @@ See the [hosting guide](/docs/guides/hosting) for details on headers and setup.
 
 BrowserPod currently supports Node.js runtime, support for Python and Ruby is coming soon.
 
-
 ## Community and support
 
 <LinkButton

sites/browserpod/src/content/docs/10-getting-started/01-quickstart.md

@@ -27,7 +27,7 @@ npm install
 npm run dev
 ```
 
-Then, open your localhost  (for example, [http://localhost:5173/](http://localhost:5173/)) in your browser, and you should
+Then, open your localhost (for example, [http://localhost:5173/](http://localhost:5173/)) in your browser, and you should
 see something like this:
 
 ![Output of the basic template](/docs/assets/bp-quickstart.png)

sites/browserpod/src/content/docs/10-getting-started/02-expressjs.md

@@ -3,8 +3,6 @@ title: Set up a basic NPM-based project
 description: In this tutorial you will set up a simple NPM project that runs an HTTP server using Express.js
 ---
 
-
-
 During this tutorial we will set up a basic project that uses BrowserPod to run
 a web server application entirely client side in the Browser.
 
@@ -13,7 +11,7 @@ a web server application entirely client side in the Browser.
 You can get the source by running `npm create browserpod-quickstart@latest` and
 selecting the "Web Server" template.
 
-###  Project structure
+### Project structure
 
 The project consists of the following files and directories:
 
@@ -42,6 +40,7 @@ There are two different NPM projects at play:
   that we want to run inside BrowserPod itself. It's a simple Hello World express.js application.
 
 ## 2. Get familiar with the project files
+
 Let's go through the relevant files one by one, explaining their purpose!
 
 ### Project's package.json
@@ -234,21 +233,19 @@ await pod.run("node", ["main.js"], {
 1. First, boot your Pod as usual and pass a valid Api Key as an argument.
 
 2. Then set up a terminal in the **console** element that was added to the `index.html` file,
-so that the output of the commands ran in the Pod are visible.
+   so that the output of the commands ran in the Pod are visible.
 
 3. Register a callback that will be notified every time an http server is
-started inside the Pod. The callback takes a Portal URL as an argument: a randomly generated, publicly accessible URL that you can use to show and interact with the inner project.
+   started inside the Pod. The callback takes a Portal URL as an argument: a randomly generated, publicly accessible URL that you can use to show and interact with the inner project.
 
 4. It will be shown that the page is up and running and link to it in the `#url` div,
-and display a live rendering of it in the `#portal` iframe. Which were both set
-up in the `index.html` page.
-
-6. Then copy the project files inside the Pod, using the `copyFile` utility function.
-
-7. Finally, run some commands inside the Pod: `npm install` to install express.js
-and its dependencies, and `node main.js` to start the web server.
+   and display a live rendering of it in the `#portal` iframe. Which were both set
+   up in the `index.html` page.
 
+5. Then copy the project files inside the Pod, using the `copyFile` utility function.
 
+6. Finally, run some commands inside the Pod: `npm install` to install express.js
+   and its dependencies, and `node main.js` to start the web server.
 
 ## End result
 

sites/browserpod/src/content/docs/11-explanation/01-api-key.md

@@ -8,7 +8,7 @@ An API key is a secret code that lets your app access a BrowserPod API. It ident
 ## Register for an API key
 
 1. Register at https://console.browserpod.io
-2.  Create a key in **Keys & Domains**
+2. Create a key in **Keys & Domains**
 
 ## Where to store the API key
 

sites/browserpod/src/content/docs/12-guides/03-hosting.md

@@ -2,6 +2,7 @@
 title: Set CORS and COOP headers
 description: Cross-origin isolation for BrowserPod (COOP and COEP)
 ---
+
 This guide shows how to configure cross-origin isolation headers for hosting a BrowserPod app, with examples for both Vite (development) and nginx (production) setups.
 
 BrowserPod requires **cross-origin isolation**, which depends on two headers:
@@ -29,6 +30,7 @@ export default defineConfig({
 ```
 
 ## Production: nginx hosting setup
+
 For production hosting, configure nginx to serve the headers so BrowserPod can run with cross-origin isolation. Create a file named `nginx.conf`:
 
 ```nginx

sites/browserpod/src/content/docs/12-guides/04-native-binaries.md

@@ -10,6 +10,7 @@ BrowserPod runs Node.js in a Wasm environment. Packages that ship native binarie
 If a package has a Wasm-compatible alternative, you can use `overrides` in `package.json` to force npm to install the Wasm version.
 
 ### Example: esbuild
+
 To use the Wasm version of `esbuild`:
 
 ```json
@@ -19,20 +20,25 @@ To use the Wasm version of `esbuild`:
 	}
 }
 ```
+
 This forces npm to replace the default `esbuild` package (which contains native binaries) with the Wasm-compatible version.
 
 ### Example: rollup
+
 Similarly, for `rollup`:
+
 ```json
 {
 	"overrides": {
 		"rollup": "npm:@rollup/wasm-node@*"
 	}
 }
 ```
+
 This ensures that the build works inside BrowserPod without relying on native CPU binaries.
 
 ## When no Wasm build exists
+
 If a package does not offer a Wasm build, it will not work inside BrowserPod. In that case, you have two options:
 
 1. Look for a different package that offers similar functionality and has a Wasm build.

sites/browserpod/src/content/docs/12-guides/05-common-errors.md

@@ -11,18 +11,19 @@ This page maps common BrowserPod error messages to their likely causes and fixes
 
 - **Causes**:
 
-    - `pod.run` is like `execve` in Linux or `child_process.spawn` in Node.
-It does not support shell features like `||` or `&&` or builtins.
+      - `pod.run` is like `execve` in Linux or `child_process.spawn` in Node.
 
-    - Bash support is on the roadmap.
+  It does not support shell features like `||` or `&&` or builtins.
+
+      - Bash support is on the roadmap.
 
 - **Solution**: Write complex behavior as a JavaScript script, and execute that.
 
 ## Missing or hidden terminal element
 
 - **Symptoms**:
-    - `The 'terminal' argument is required`
-    - Output disappears during long runs
+  - `The 'terminal' argument is required`
+  - Output disappears during long runs
 
 - **Cause**: The terminal element was never created or was unmounted.
 
@@ -34,8 +35,6 @@ const terminal = await pod.createDefaultTerminal(consoleEl);
 pod.run(..., {terminal,...});
 ```
 
-
-
 ## Using the wrong file mode
 
 - **Symptom**: `Unsupported 'mode' argument`
@@ -51,4 +50,4 @@ pod.run(..., {terminal,...});
 - **Cause**: Native binaries do not run in the Wasm environment.
 
 - **Solution**: Use Wasm alternatives and `package.json` overrides. See the
-[native binaries guide](/docs/guides/native-binaries).
+  [native binaries guide](/docs/guides/native-binaries).

sites/browserpod/src/content/docs/13-reference/00-BrowserPod/02-onPortal.md

@@ -19,4 +19,5 @@ class BrowserPod {
 - **port (`number`)** - The local port that is connected to the Portal.
 
 ## Returns
+
 `onPortal` does not return a value.

sites/browserpod/src/content/docs/13-reference/01-BinaryFile/02-getSize.md

@@ -8,8 +8,11 @@ class BinaryFile {
 	async getSize(): Promise<int>;
 }
 ```
+
 ## Parameters
+
 `getSize` does not have any parameters.
+
 ## Returns
 
 `getSize` returns a [Promise] which is resolved when the operation has succeded.

sites/browserpod/src/content/docs/13-reference/01-BinaryFile/03-close.md

@@ -8,7 +8,9 @@ class BinaryFile {
 	async close(): Promise<void>;
 }
 ```
+
 ## Parameters
+
 `close` does not have any parameters.
 
 ## Returns