chore(ts): Update typescript dependencies

examples/typescript-vitest/package.json

@@ -3,7 +3,7 @@
   "version": "0.3.0",
   "private": true,
   "type": "module",
-  "packageManager": "pnpm@11.15.0",
+  "packageManager": "pnpm@11.15.1",
   "scripts": {
     "build": "tsc -p tsconfig.json",
     "test": "vitest run",

renovate.json5

@@ -74,6 +74,26 @@
       groupName: "typescript dependencies",
       commitMessagePrefix: "chore(ts):",
     },
+    {
+      // The website type-checks and transpiles the example editors IN THE
+      // BROWSER (packages/website/src/lib/{ts-diagnostics,run-worker}.ts).
+      // TypeScript 7 is the native Go compiler: `import * as ts from
+      // 'typescript'` resolves to a module exporting a version string and
+      // nothing else, and the real API spawns a binary over a pipe. There is no
+      // WASM build of tsgo yet (microsoft/typescript-go#3478, #4633) — the
+      // official Playground is itself still on 6.x. @astrojs/check pins to
+      // ^5 || ^6 besides, so a 7 bump here fails the build outright.
+      //
+      // Renovate groups all npm into one PR, so without this the website rides
+      // along on any TypeScript bump aimed at the rest of the workspace, which
+      // is on 7 deliberately. `typescript/pnpm-workspace.yaml`'s
+      // updateConfig.ignoreDependencies is the same guard for local
+      // `pnpm update --latest` runs. Drop both when tsgo runs in a browser.
+      matchManagers: ["npm"],
+      matchFileNames: ["typescript/packages/website/package.json"],
+      matchPackageNames: ["typescript"],
+      allowedVersions: "<7",
+    },
     {
       matchManagers: ["pep621", "pip_requirements", "pip-compile"],
       groupName: "python dependencies",

typescript/package.json

@@ -6,7 +6,7 @@
   "engines": {
     "node": ">=22.18"
   },
-  "packageManager": "pnpm@11.15.0",
+  "packageManager": "pnpm@11.15.1",
   "scripts": {
     "build": "pnpm -r --filter '!@varar/website' --filter '!@varar/website' build",
     "typecheck": "tsc -p tsconfig.tests.json",

typescript/packages/config/src/config.ts

@@ -2,8 +2,6 @@ import { existsSync, readFileSync } from 'node:fs'
 import { resolve } from 'node:path'
 import type { Config, Globs, ParsedConfig } from './config-types.ts'
 
-export type { Config, Globs, ParsedConfig } from './config-types.ts'
-
 const EMPTY_PARSED: ParsedConfig = {
   // No default docs OR steps globs: a repo must declare both explicitly.
   // (The old TS-only `**/*.steps.ts` steps default died with the TS-only

typescript/packages/vscode/package.json

@@ -55,7 +55,7 @@
     "vscode-languageclient": "^10.1.0"
   },
   "devDependencies": {
-    "@types/vscode": "~1.105.0",
+    "@types/vscode": "~1.125.0",
     "esbuild": "^0.28.1"
   },
   "license": "MIT",

typescript/pnpm-workspace.yaml

@@ -2,6 +2,22 @@ packages:
   - packages/*
   - ../examples/typescript-vitest
 
+# `pnpm update --latest` ignores the semver ranges in package.json, so nothing
+# written in a manifest can stop it walking packages/website from typescript 6
+# to 7 — which silently breaks the example editors, since 7 is the native Go
+# compiler with no in-process API to type-check or transpile with in a browser
+# (see the Stack section of CLAUDE.md). This list is the only thing that holds
+# it: `pnpm.updateConfig` in a workspace member's own package.json is read by
+# nothing, and only the entry here takes effect.
+#
+# It is name-based and workspace-wide, so it also parks the ROOT's typescript at
+# the next release — `pnpm up -rL` will not move it to 7.1 on its own. That is
+# deliberate: a compiler upgrade is a decision, not a drive-by. Naming the
+# package explicitly (`pnpm up -L typescript`) overrides this list.
+updateConfig:
+  ignoreDependencies:
+    - typescript
+
 # Dependencies allowed to run install scripts. pnpm blocks them by default as a
 # supply-chain measure and fails the install (exit 1, in CI as much as
 # interactively) until each one is decided either way.