From 4e2383994ff481e91c0a7fc9ef07b691f1c87801 Mon Sep 17 00:00:00 2001
From: Olli Paloviita <olli.paloviita@gmail.com>
Date: Tue, 26 May 2026 19:06:43 +0300
Subject: [PATCH] docs(screenci): update installation guide

---
 docs/installation.mdx | 4 ++--
 package.json          | 6 ------
 pnpm-workspace.yaml   | 6 ++++++
 3 files changed, 8 insertions(+), 8 deletions(-)
 create mode 100644 pnpm-workspace.yaml

diff --git a/docs/installation.mdx b/docs/installation.mdx
index 75fb012..6e03a3d 100644
--- a/docs/installation.mdx
+++ b/docs/installation.mdx
@@ -11,7 +11,7 @@ Then ScreenCI allows converting these tests into product videos with `record` co
 #### You will learn
 
 - [how to install ScreenCI](#install-screenci)
-- [what `screenci init` creates](#what-gets-created)
+- [what initializing creates](#what-initializing-creates)
 - [how to run the starter script locally](#run-the-example)
 - [how to record the first final video](#record-the-final-result)
 
@@ -51,7 +51,7 @@ If you already know Playwright, the closest mental model is Playwright's own
 browser automation stack, but the output is a maintained video instead of a
 test suite.
 
-## What gets created
+## What initializing creates
 
 The generated project includes the config, starter video script, and a few
 supporting files for a first usable run. If you accepted the optional GitHub
diff --git a/package.json b/package.json
index 8f1c9b5..a2e0402 100644
--- a/package.json
+++ b/package.json
@@ -82,11 +82,5 @@
     "ora": "^9.3.0",
     "picocolors": "^1.1.1",
     "playwright-recorder-plus": "^0.1.3"
-  },
-  "pnpm": {
-    "onlyBuiltDependencies": [
-      "esbuild",
-      "ffmpeg-static"
-    ]
   }
 }
diff --git a/pnpm-workspace.yaml b/pnpm-workspace.yaml
new file mode 100644
index 0000000..ce484cb
--- /dev/null
+++ b/pnpm-workspace.yaml
@@ -0,0 +1,6 @@
+packages:
+  - .
+
+allowBuilds:
+  esbuild: true
+  ffmpeg-static: true