From 03ac0ce979d179301bcdc621c589b97e11857d8a Mon Sep 17 00:00:00 2001 From: Tudor Zaharia Date: Mon, 10 Aug 2026 11:05:17 +0200 Subject: [PATCH 1/4] minor fix website docs --- docs/extensions/development.md | 2 -- 1 file changed, 2 deletions(-) diff --git a/docs/extensions/development.md b/docs/extensions/development.md index c89ae8a1f..a34291708 100644 --- a/docs/extensions/development.md +++ b/docs/extensions/development.md @@ -112,8 +112,6 @@ PGlite's frontend code is in the main [PGlite repo](https://github.com/electric- You will need to create a new package for your extension. The easiest way is to just copy the files from an existing extension package such as `packages/pglite-pgvector`. Obviously, you will need to adapt all the references to the previous extension. -``` - To make it available in our online [REPL](https://pglite.dev/repl/), add the extension to `docs/repl/allExtensions.ts`: ``` From 91efa013a57765c8a18660446e5b092fe691f919 Mon Sep 17 00:00:00 2001 From: Tudor Zaharia Date: Mon, 10 Aug 2026 11:05:57 +0200 Subject: [PATCH 2/4] style --- docs/extensions/development.md | 3 +++ 1 file changed, 3 insertions(+) diff --git a/docs/extensions/development.md b/docs/extensions/development.md index a34291708..80f3a9ed9 100644 --- a/docs/extensions/development.md +++ b/docs/extensions/development.md @@ -184,4 +184,7 @@ As mentioned before, some extensions require more effort to integrate with PGlit Another source of pain for building an extension is the need to export symbols from the dependencies or from PGlite itself. Sometimes these are obvious only at runtime. We are still working on documentation and examples showing how to build more complex Postgres extensions for use with PGlite. Please check back soon, or reach out on [Discord](https://discord.com/channels/933657521581858818/1212676471588520006) if you would like to try building a particular extension for PGlite. + +``` + ``` From 1ed420410f7ded3873e900e908f3a80a27de6244 Mon Sep 17 00:00:00 2001 From: Tudor Zaharia Date: Mon, 10 Aug 2026 11:07:13 +0200 Subject: [PATCH 3/4] leftovers --- docs/extensions/development.md | 3 --- 1 file changed, 3 deletions(-) diff --git a/docs/extensions/development.md b/docs/extensions/development.md index 80f3a9ed9..9a6213d15 100644 --- a/docs/extensions/development.md +++ b/docs/extensions/development.md @@ -185,6 +185,3 @@ Another source of pain for building an extension is the need to export symbols f We are still working on documentation and examples showing how to build more complex Postgres extensions for use with PGlite. Please check back soon, or reach out on [Discord](https://discord.com/channels/933657521581858818/1212676471588520006) if you would like to try building a particular extension for PGlite. -``` - -``` From 6119a000033ecc77bf736b6f2b0de8e22c948e10 Mon Sep 17 00:00:00 2001 From: Tudor Zaharia Date: Mon, 10 Aug 2026 11:07:59 +0200 Subject: [PATCH 4/4] cleanup --- docs/extensions/development.md | 1 - 1 file changed, 1 deletion(-) diff --git a/docs/extensions/development.md b/docs/extensions/development.md index 9a6213d15..6ab15364d 100644 --- a/docs/extensions/development.md +++ b/docs/extensions/development.md @@ -184,4 +184,3 @@ As mentioned before, some extensions require more effort to integrate with PGlit Another source of pain for building an extension is the need to export symbols from the dependencies or from PGlite itself. Sometimes these are obvious only at runtime. We are still working on documentation and examples showing how to build more complex Postgres extensions for use with PGlite. Please check back soon, or reach out on [Discord](https://discord.com/channels/933657521581858818/1212676471588520006) if you would like to try building a particular extension for PGlite. -