chore: migrate to hoistPattern and fix vitepress build

Switch from `hoist: false` to `hoistPattern: ['*', '!@types/bun']` and
install packages that were missing due to shamefullyHoist being disabled,
which broke the vitepress build in the previous commit.

Author: dinwwwh

apps/content/package.json

@@ -30,10 +30,12 @@
     "@tanstack/svelte-query": "^6.1.34",
     "@tanstack/vue-query": "^5.101.0",
     "@types/node": "^26.0.1",
+    "@vueuse/core": "^14.3.0",
     "effect": "4.0.0-beta.90",
     "markdown-it-task-lists": "^2.1.1",
     "mermaid": "^11.15.0",
     "openai": "^6.44.0",
+    "pino": "^10.3.1",
     "superjson": "^2.2.6",
     "vitepress": "1.6.4",
     "vitepress-plugin-group-icons": "^1.7.5",

pnpm-lock.yaml

@@ -3,12 +3,14 @@ packages:
   - 'packages/*'
   - 'playgrounds/*'
 
-# Disable hoisting: @types/node and @types/bun, when installed in different
-# packages, both get hoisted into the same env. This conflicts and breaks
-# type checking when working on node.js types alongside a package that imports from 'bun'.
-# Alternative: use https://pnpm.io/settings#hoistpattern to exclude only
-# @types/bun instead of disabling hoisting entirely.
-hoist: false
+# Hoist everything (default) except @types/bun. When @types/node and @types/bun are
+# installed in different packages, hoisting both into the same env causes a
+# conflict and breaks type checking when working on Node.js types alongside
+# a package that imports from 'bun'. Excluding @types/bun from hoisting
+# avoids this while keeping hoisting enabled for everything else.
+hoistPattern:
+  - '*'
+  - '!@types/bun'
 
 # Lets playgrounds/* resolve local packages without the 'workspace:' protocol
 # during development. When a playground is cloned standalone, the same