@enfocussw/switch-scripting-context 0.1.0

package/docs/switch-project/tooling.md

@@ -0,0 +1,165 @@
+---
+id: tooling
+category: switch-project
+order: 11
+summary: "SwitchScriptTool commands and install paths, folder vs `.sscript` trade-offs, deployment"
+triggers:
+  - "Running SwitchScriptTool: transpiling, packing, unpacking, or deploying"
+---
+
+# Script Folders, Packages & SwitchScriptTool
+
+<!-- docs-index:contents begin -->
+## Contents
+
+- Script folder vs script package
+- SwitchScriptTool
+- Commands
+- Verify entry points before packing
+- Deployment
+<!-- docs-index:contents end -->
+
+## Script folder vs script package
+
+| | Script folder | Script package (`.sscript`) |
+|---|---|---|
+| Use for | Development, version control | Production, deployment |
+| Included in flow export | **No** | Yes |
+| TypeScript transpile | Manual — `SwitchScriptTool --transpile` | Automatic in SwitchScripter |
+| Password protection | Not supported | Optional |
+| Can be used as App | No — must pack first | Yes |
+
+Script folders are not included in flow exports or backups. Never use a script folder in production — pack it to a `.sscript` package first.
+
+## SwitchScriptTool
+
+Command-line tool included with Switch. May not be on `PATH` — fall back to the known install
+location for the current OS if the bare command isn't found.
+
+**Windows:** `C:\Program Files\Enfocus\Enfocus Switch\SwitchScriptTool\SwitchScriptTool.exe` (add to PATH to avoid typing the full path)
+
+**macOS:** symlinked to `/usr/local/bin/SwitchScriptTool` by the installer. If the symlink is missing, the real binary is bundled inside the SwitchScripter app: `/Applications/Enfocus/Enfocus Switch/SwitchScripter.app/Contents/MacOS/SwitchScriptTool/SwitchScriptTool`.
+
+## Commands
+
+| Mode | Command | Purpose |
+|---|---|---|
+| Create | `SwitchScriptTool --create <ScriptID> <Path> [--JavaScript]` | Scaffold a new script folder with all required files |
+| Transpile | `SwitchScriptTool --transpile <Path>` | Compile `main.ts` → `main.js`. **Must use this, not `tsc` directly** |
+| Pack | `SwitchScriptTool --pack <Folder> <OutputFolder> [--password <pwd>] [--verbose]` | Create `<OutputFolder>/<ScriptID>.sscript` for deployment. `<OutputFolder>` is a directory, created if missing, not the package's file path |
+| Unpack | `SwitchScriptTool --unpack <file.sscript> <Folder> [--password <pwd>]` | Extract package to folder |
+| List | `SwitchScriptTool --list <file.sscript>` | List package contents (no password needed) |
+| Generate translations | `SwitchScriptTool --generate-translations <ScriptFolder> <ResultFolder>` | Generate translation files for the script package |
+
+**Create** scaffolds: `manifest.xml`, `<ScriptID>.xml`, `<ScriptID>.sscript`, `main.ts` (or `main.js` with `--JavaScript`), `.vscode/launch.json`, `Resources/`, plus `package.json`, `tsconfig.json`, `.vscode/switch.code-snippets`, and type declarations for TypeScript. Creates `<Path>/<ScriptID>/` — it does not write into `<Path>` directly. `ScriptID` may only contain letters, digits, hyphens, and underscores.
+
+**Gotcha: `--create` deletes an existing target folder.** If `<Path>/<ScriptID>/` already exists, `--create` removes it and everything in it (including `.git/`, a README, or AI agent config files) without prompting, then scaffolds a fresh folder. The only sign is an `Info: Removed existing target folder` line in its output. Never run `--create` where `<Path>/<ScriptID>/` exists, and never use it to turn the folder you're already working in into a script folder: `--create <FolderName> <ParentOfFolder>` wipes that folder. Check that the target doesn't exist first.
+
+**Transpile** is required after every edit to `main.ts` before testing a **script folder** directly in Switch. Switch executes `main.js` only — `main.ts` is never run directly. Using SwitchScriptTool (not `tsc`) ensures the same transpile options as SwitchScripter, which is required for consistent behavior. This step is **not** needed before packing — see Pack below.
+
+**Pack** transpiles `main.ts` fresh into the package on every run; it never reads or modifies any `main.js` already sitting in the source folder (a stale hand-edited `main.js` there is ignored and left untouched).
+
+Pack copies an allowlist of files, not the whole folder. Only these end up in the `.sscript`: `manifest.xml`, the declaration file named in `ScriptDeclarationFile`, the program file named in `ScriptProgramFiles` plus the `main.js` and `main.js.map` pack transpiles from it, the icon named in `ScriptIconFile`, `tsconfig.json`, the placeholder `<ScriptID>.sscript`, `Resources/`, and `node_modules/`. Everything else in the folder is left out and printed in an "Info: ... will not be packed" list, even without `--verbose`. That includes `package.json`, `package-lock.json`, `.vscode/`, a README, other `.ts`/`.js` files, subfolders other than `Resources/` and `node_modules/`, and AI agent config and docs folders. `--verbose` additionally prints the full list of what *will* be packed. Translation files were not part of this test. Verified with a pre-release SwitchScriptTool build.
+
+`node_modules` is packed as-is, so run `npm prune --production` first (see Deployment) — otherwise `devDependencies` (including `@types/*` packages, which the scaffolded `package.json` puts there) get bundled into the package for no runtime benefit. One harmless quirk: the placeholder `<ScriptID>.sscript` file scaffolded by `--create` is on the allowlist and ends up packed inside the real `.sscript` too. Pack also replaces `SwitchVersion` in the packed `manifest.xml` with SwitchScriptTool's own version (`--create` writes it too), and that value picks the Node.js version the package runs on. See [node-versions.md § What writes `SwitchVersion`](node-versions.md#what-writes-switchversion).
+
+**Gotcha: local modules break pack.** A `main.ts` that imports a local module (`import { x } from './helper'` or `'./lib/helper'`) fails to pack with TypeScript error TS2307 (`Cannot find module`), and no `.sscript` is written. Pack's own output shows why: `helper.ts` and `lib/helper.ts` appear in its "will not be packed" list, and the TS2307 error points at pack's temporary copy of the folder, which doesn't contain them. A `main.js` that `require`s a local file was not tested, but that file isn't packed either. The manifest also accepts only one `ScriptProgramFile` (pack errors with `The manifest must contain only one script program file`), so listing the helper there doesn't work. The verified option is to keep script code in the single program file. Shared code in an npm package under `node_modules/` might work, since `node_modules/` is packed, but that was not tested, and neither was a `file:` dependency, which npm installs as a symlink.
+
+**Unpack** prints package metadata (`Type`, `Protection`, `Status`) before extracting. For a TypeScript-sourced package it extracts only `main.ts` — the compiled `main.js`/`main.js.map` are not written back out, so a pack → unpack round trip returns a clean, editable script folder rather than a compiled snapshot.
+
+## Verify entry points before packing
+
+Switch's entry-point scanner is regex-based, not a real parser, and can silently drop entry-point
+functions from certain string/regex/division shapes — see
+[entry-points.md § Entry-point scanner constraints](../switch-api/entry-points.md#entry-point-scanner-constraints).
+`--pack` does not validate or warn about this: a script that packs cleanly can still fail to load,
+or load with a property callback that silently never runs. Compiling and passing tests doesn't
+catch it either, since the source is syntactically valid JS/TS — only extraction against the built
+`main.js` does.
+
+After any edit to `main.ts`/`main.js`, run the extracted entry points against the **built**
+`main.js` and confirm the expected names come back. Python:
+
+```python
+#!/usr/bin/env python3
+import re, sys
+
+STRIP_PATTERN = re.compile(
+    r'(?:/\*.*?\*/)'
+    r'|(?:(["\'`])\1)'
+    r'|(?://.*?$)'
+    r'|(?:([/"\'`]).*?[^\\]\2)'
+    r'|(?:/(?:\\.|[^/\n])*/)'
+    r'|(?:\(\s*\w+\s*/\s*\w+\s*\))'
+    r'|(?:\w+\s*/\s*\w+)',
+    re.DOTALL | re.MULTILINE,
+)
+FUNC_PATTERN = re.compile(r'function[\s\n\r]+(\$?\w+)[\s\n\r]*\(', re.MULTILINE)
+NODE_ENTRY_POINTS = {
+    'timerFired', 'jobArrived', 'getLibraryForProperty', 'getLibraryForConnectionProperty',
+    'findExternalEditorPath', 'validateProperties', 'validateConnectionProperties',
+    'httpRequestTriggeredSync', 'httpRequestTriggeredAsync', 'flowStopTriggered',
+    'flowStartTriggered', 'abort',
+}
+REQUIRED_ANY = {'jobArrived', 'timerFired', 'flowStopTriggered', 'httpRequestTriggeredAsync'}
+
+code = open(sys.argv[1], encoding='utf-8').read()
+stripped = STRIP_PATTERN.sub('', code)
+found = [m.group(1) for m in FUNC_PATTERN.finditer(stripped) if m.group(1) in NODE_ENTRY_POINTS]
+print('Entry points found:', found or '(none)')
+if not (REQUIRED_ANY & set(found)):
+    sys.exit('FAIL: none of ' + str(sorted(REQUIRED_ANY)) + ' survived extraction.')
+```
+
+Or Node.js:
+
+```js
+#!/usr/bin/env node
+const fs = require('fs');
+
+const STRIP_PATTERN = /(?:\/\*[\s\S]*?\*\/)|(?:(["'`])\1)|(?:\/\/.*?$)|(?:([/"'`])[\s\S]*?[^\\]\2)|(?:\/(?:\\.|[^/\n])*\/)|(?:\(\s*\w+\s*\/\s*\w+\s*\))|(?:\w+\s*\/\s*\w+)/gm;
+const FUNC_PATTERN = /function[\s\n\r]+(\$?\w+)[\s\n\r]*\(/gm;
+const NODE_ENTRY_POINTS = new Set([
+  'timerFired', 'jobArrived', 'getLibraryForProperty', 'getLibraryForConnectionProperty',
+  'findExternalEditorPath', 'validateProperties', 'validateConnectionProperties',
+  'httpRequestTriggeredSync', 'httpRequestTriggeredAsync', 'flowStopTriggered',
+  'flowStartTriggered', 'abort',
+]);
+const REQUIRED_ANY = ['jobArrived', 'timerFired', 'flowStopTriggered', 'httpRequestTriggeredAsync'];
+
+const stripped = fs.readFileSync(process.argv[2], 'utf8').replace(STRIP_PATTERN, '');
+const found = [];
+let m;
+while ((m = FUNC_PATTERN.exec(stripped)) !== null) {
+  if (NODE_ENTRY_POINTS.has(m[1])) found.push(m[1]);
+}
+console.log('Entry points found:', found.length ? found : '(none)');
+if (!found.some((f) => REQUIRED_ANY.includes(f))) {
+  console.error('FAIL: none of', REQUIRED_ANY, 'survived extraction.');
+  process.exit(1);
+}
+```
+
+If the required entry point is missing, dump `stripped`/the stripped output and diff it against
+`main.js` — the first swallowed region starts at the string, regex, or division literal identified
+in the rules above.
+
+## Deployment
+
+Before packing, remove dev dependencies to reduce package size — this matters because `--pack` bundles `node_modules` as-is, and the scaffolded `package.json` puts type-only packages (`@types/node`, `@types/switch-scripting`, `undici-types`) under `devDependencies`:
+
+```
+npm prune --production
+```
+
+Then pack:
+
+```
+SwitchScriptTool --pack <ScriptFolder> <OutputFolder>
+```
+
+Reasons not to use a script folder in production:
+- Not included in flow exports or backups
+- Slower execution than a package
+- Any syntax error saved to `main.js` immediately breaks the running script
+- No password protection available

package/docs/switch-project/vscode.md

@@ -0,0 +1,90 @@
+---
+id: vscode
+category: switch-project
+order: 13
+summary: "Type declarations, tsconfig for TypeScript 6, ESLint rules, entry point snippets"
+triggers:
+  - "Setting up VS Code or fixing type errors"
+---
+
+# VS Code Setup
+
+## Type declarations
+
+Enables autocomplete and type checking for `Switch`, `Job`, `FlowElement` and all Switch API globals.
+
+**Via npm (preferred):** Add to `devDependencies` in `package.json` and run `npm install`:
+
+```json
+"@types/switch-scripting": "https://github.com/enfocus-switch/types-switch-scripting/archive/refs/tags/v24.1.1-final.tar.gz"
+```
+
+**Manual fallback:** Download `index.d.ts` from the types repo and place it at `node_modules/@types/switch-scripting/index.d.ts` inside the script folder.
+
+> `SwitchScriptTool --create` sets this up automatically for new TypeScript script folders.
+
+v24.1.1-final is the last published version and matches the API of every Switch release from 24.1
+to 26.11. It declares every method without marking which Switch release added it, so the compiler
+won't flag a call that an older target Switch lacks. Check those against
+[api-versions.md](../switch-api/api-versions.md).
+
+SwitchScriptTool 26.11 also scaffolds `@types/node` 24.x whatever Node.js version the script will
+run on. When the package will run on an older Node.js (see
+[node-versions.md](node-versions.md)),
+pin `@types/node` to that major version so the compiler flags newer Node.js APIs.
+
+## TypeScript 6 / VS Code 1.114+
+
+From VS Code 1.114, TypeScript 6 is used. Ambient/global types are no longer auto-included — without explicit configuration, `@types/node` and `@types/switch-scripting` globals (`Switch`, `Job`, etc.) will not be recognised.
+
+Add a `types` array to `compilerOptions` in `tsconfig.json`:
+
+```json
+{
+  "compilerOptions": {
+    "types": ["node", "switch-scripting"]
+  }
+}
+```
+
+## ESLint rules
+
+Two rules that catch Switch-specific async bugs before runtime:
+
+- **`require-await`** — flags `async` functions that never actually `await`, catching accidentally dropped API call promises
+- **`@typescript-eslint/no-floating-promises`** — errors on any unawaited promise; in Switch scripts these cause silent race conditions that are very difficult to diagnose
+
+Example `.eslintrc`:
+
+```json
+{
+  "root": true,
+  "parser": "@typescript-eslint/parser",
+  "parserOptions": { "project": "./tsconfig.json" },
+  "plugins": ["@typescript-eslint", "prettier"],
+  "extends": [
+    "eslint:recommended",
+    "plugin:@typescript-eslint/eslint-recommended",
+    "plugin:@typescript-eslint/recommended",
+    "prettier"
+  ],
+  "rules": {
+    "require-await": 2,
+    "@typescript-eslint/no-floating-promises": 2,
+    "prettier/prettier": 2
+  }
+}
+```
+
+## Snippets
+
+`SwitchScriptTool --create` generates `.vscode/switch.code-snippets` for TypeScript scripts only; a
+`--JavaScript` scaffold gets none. The file has one snippet per entry point, 13 in all (checked with
+SwitchScriptTool 26.11). Each prefix is `switch` followed by the entry point name, for example
+`switchJobArrived` or `switchHttpRequestTriggeredSync`. The one exception is
+`switchfindExternalEditorPath`, with a lowercase `f`. Each snippet inserts an empty top-level
+`async function` with the signature from [entry-points.md](../switch-api/entry-points.md), without
+`export`.
+
+Snippets expand only when a person types the prefix in VS Code. An agent writing `main.ts` copies the
+signature from `entry-points.md` instead.

package/docs/switch-scripting.md

@@ -0,0 +1,70 @@
+# Switch Scripting (Node.js)
+Enfocus Switch workflow automation scripts written in TypeScript/Node.js.
+
+Read the matching file from the API reference table below before answering any question about Switch scripting, not only before writing code. This applies to short and yes/no questions too. This page only summarises; the answer usually depends on a detail that is only in the linked file, and Switch often differs from what general Node.js or scripting knowledge suggests.
+
+## Execution environment
+- Entry points are top-level `async` functions with specific names — **not exported** — executed in a `node:vm.Script()` context.
+- ESM is supported: if ES modules are present the script is bundled with ESBuild before running (when `SwitchVersion` in `manifest.xml` is `24.0` or higher).
+- Type declarations are in `node_modules/@types/switch-scripting/index.d.ts` and must be followed precisely. They list every method up to Switch 24.1 without saying which release added it.
+- The Node.js version comes from `SwitchVersion` in `manifest.xml`; the available API methods come from the Switch version the script runs on. See `switch-project/node-versions.md` and `switch-api/api-versions.md`.
+
+## API reference
+Detailed docs live in three folders, alongside this file: `switch-api/` (the scripting API itself),
+`switch-project/` (script/app project structure and tooling), and `switch-appstore/` (Appstore
+publishing guidance).
+
+<!-- docs-index:table begin -->
+| File | Contents | Load when |
+|---|---|---|
+| `switch-project/project-planning.md` | Planning checklist, run before scaffolding or on a project that is already scaffolded: Script vs App, job-processing approach, one script folder or several, target OS, Switch version baseline, concurrency, native/binary npm dependencies, Appstore competition risk | Starting a new script or app, before scaffolding any files, or working in a script folder that is already scaffolded where Script vs App has not been settled |
+| `switch-api/entry-points.md` | All entry point signatures, constraints, and when each is called | Scaffolding a script, adding/editing an entry point, or making any edit to main.ts/main.js |
+| `switch-api/switch.md` | `Switch` (`s`): global data, webhooks, abort, server utilities | Using global data, webhooks, abort, or server settings |
+| `switch-api/flow-element.md` | `FlowElement`: properties, connections, job creation, logging | Reading properties, creating jobs, logging, connections |
+| `switch-api/job.md` | `Job` **signatures**: routing, file access, child jobs, private data, datasets | Looking up what a `job.*` method takes, returns, or throws |
+| `switch-api/connection.md` | `Connection`: type, properties, file count | Routing to specific connections or reading connection properties |
+| `switch-api/http.md` | `HttpRequest` / `HttpResponse` + webhook pattern | Handling incoming HTTP webhooks |
+| `switch-api/enums.md` | All enums with string values (`LogLevel`, `AccessLevel`, `DatasetModel`, `Scope`, `Priority`, `Connection.Level`, etc.) | Looking up enum values |
+| `switch-api/document-classes.md` | `PdfDocument`, `PdfPage`, `ImageDocument`, `XmlDocument`, `XmpDocument`: read-only file introspection | Inspecting PDF, image, XML, or XMP file contents |
+| `switch-project/script-structure.md` | What files a script folder contains, laying out several script folders side by side, `manifest.xml` format, Script vs App, packing an app with SwitchScripter | Setting up a new script project or converting a Script to an App |
+| `switch-project/tooling.md` | SwitchScriptTool commands and install paths, folder vs `.sscript` trade-offs, deployment | Running SwitchScriptTool: transpiling, packing, unpacking, or deploying |
+| `switch-project/debugging.md` | Enabling debug mode in Switch Designer, debuggable entry points, VS Code attach | Debugging a script |
+| `switch-project/vscode.md` | Type declarations, tsconfig for TypeScript 6, ESLint rules, entry point snippets | Setting up VS Code or fixing type errors |
+| `switch-project/script-declaration.md` | XML declaration reference: properties, connections, execution config; agents may edit this file directly | Understanding, adding, or editing script properties/connections/execution config |
+| `switch-project/property-editors.md` | Property editor types, string return values, literal editors, dropdowns | Defining property editors in XML or reading property values in code |
+| `switch-api/job-patterns.md` | `Job` **rules and gotchas**: file access semantics, temp cleanup, which `sendTo*()` suits which connection type, dataset/child ordering, locking shared global data, executor limits | Writing or reviewing job-handling code. Pair with `job.md` when you also need signatures |
+| `switch-api/execution-environment.md` | Execution modes (`Concurrent`/`Serialized`, `ExecutionGroup`, `NumberOfSlots`), process/concurrency model, state persistence across job invocations, unhandled-rejection behavior, npm/native module constraints | Choosing or changing an execution mode, relying on module-level state across jobs, handling errors/rejections, or using third-party npm packages |
+| `switch-api/logging.md` | Log level semantics, logging practice, `console.log` limitation, common gotchas | Adding or reviewing `job.log()`/`flowElement.log()`/`job.fail()`/`failProcess()` calls |
+| `switch-project/logs-and-dataroot.md` | Locating the Application Data Root, querying `ServerLogs.db3` directly | Diagnosing or validating a script from its actual log output rather than by reading the code |
+| `switch-appstore/app-guidelines.md` | Pre-publish checklist for Appstore apps: property naming/tooltips/editors, entry point and sendTo consistency, logging quality, packaging, and the app-only submission rules (localization, signed universal macOS binaries) | Preparing a script for publication as an app, or reviewing one against Appstore submission criteria |
+| `switch-project/property-documentation.md` | Writing guidance for `Tooltip` and `DetailedInfo` content on properties/connections | Writing or reviewing the text in a property's or connection's `Tooltip`/`DetailedInfo` |
+| `switch-appstore/app-store-listing.md` | Writing guidance for the declaration's Appstore listing fields: `Description`, `Compatibility`, `SupportInfo`, `AppDiscovery`, `Connections` | Writing or reviewing the app's Appstore listing text |
+| `switch-appstore/app-manual.md` | Writing guidance for the separate app manual document uploaded during Appstore review (`documentation-app_name.docx` template) | Preparing the app manual document for Appstore submission |
+| `switch-appstore/app-store-submission.md` | Writing guidance for the Create Appstore App / Create Appstore App Version web forms: Short Description, What's new, Eula, icon specs, and which fields reuse content already written elsewhere | Preparing content for the Appstore website submission forms |
+| `switch-api/api-versions.md` | Which Switch release added each scripting API class, method, and enum value; API availability follows the running Switch, not `manifest.xml` | Writing or reviewing code for a script or app that must run on a Switch version older than the latest, or when the user names a minimum Switch version |
+| `switch-project/node-versions.md` | How `SwitchVersion` in `manifest.xml` selects the Node.js version, the version table per Switch release, which tools overwrite `SwitchVersion`, values missing from the table, other effects of `SwitchVersion` | Working out which Node.js version a script or app will run on, or what `SwitchVersion` in manifest.xml does |
+<!-- docs-index:table end -->
+
+## Key rules
+- Before scaffolding a new script or app, work through `switch-project/project-planning.md` with the user.
+  If the script folder is already scaffolded, still ask Script or App; the manifest cannot answer it.
+- If the script or app must run on a Switch version older than the latest, check each API call
+  against `switch-api/api-versions.md`. The API files mark anything newer than the baseline with
+  "Switch X+" (a `// Switch X+` comment above a signature, or a note in the text), meaning that
+  version or later.
+- To find documented behavioural pitfalls before writing code in an area, grep the `switch-api/`,
+  `switch-project/`, and `switch-appstore/` docs folders for `known issue`, `gotcha`,
+  `quirk`, `caveat` (case-insensitive) — every documented pitfall uses one of these four terms.
+- Do not `export` entry point functions. Declare them with the literal `function` keyword at top
+  level — arrow functions, `exports.name = ...`, and class methods are invisible to Switch.
+- Switch discovers entry points with a regex, not a parser. Never write a string literal whose
+  content ends with a backslash, a regex literal, or division outside the plain `word / word`
+  shape — each silently deletes a span of real code, and every entry point inside that span
+  disappears with no error anywhere. Read `switch-api/entry-points.md` §
+  Entry-point scanner constraints before editing `main.ts`/`main.js`.
+- Every `jobArrived` invocation must end with exactly one `job.sendTo*()` or `job.fail()` call — either in the same invocation or deferred to `timerFired` via job information stored in global data.
+- Use `AccessLevel.ReadOnly` for `job.get()` unless the file content will be modified.
+- After editing `main.ts`, transpile with `SwitchScriptTool --transpile <folder>`. Do not use `tsc` directly.
+- Never use a script folder in production. Pack it with `SwitchScriptTool --pack` first; flow exports and backups leave script folders out.
+- After calling `createJob()`, `createChild()`, or `createDataset()` with a file path, the script must delete the source file/folder after routing — Switch does not auto-remove it.
+- The XML declaration (`<ScriptID>.xml`) can be edited directly — read `switch-project/script-declaration.md` first and follow its rules exactly (no schema validates this format, so mistakes fail silently). Never change an existing script's `Name`. Bump `Version` only when the current value has already been released, not on every edit. Leave `manifest.xml` edits (package type, declaration filename, program files) to the user unless explicitly asked.

package/package.json

@@ -0,0 +1,65 @@
+{
+  "name": "@enfocussw/switch-scripting-context",
+  "version": "0.1.0",
+  "description": "AI coding assistant context for Enfocus Switch scripting (Node.js/TypeScript)",
+  "keywords": [
+    "switch",
+    "enfocus",
+    "switch-scripting",
+    "ai-context",
+    "claude",
+    "copilot",
+    "cursor",
+    "codex",
+    "gemini",
+    "windsurf",
+    "zed",
+    "cline"
+  ],
+  "main": "dist/init.js",
+  "bin": {
+    "switch-scripting-context": "bin/cli.js"
+  },
+  "files": [
+    "bin/",
+    "dist/",
+    "!dist/*.test.js",
+    "docs/",
+    "!docs/superpowers",
+    "!docs/temp",
+    "!docs/adr",
+    "CHANGELOG.md"
+  ],
+  "scripts": {
+    "build": "tsc -p tsconfig.json",
+    "build:test": "tsc src/init.test.ts --outDir dist --target ES2020 --module commonjs --lib ES2020 --types node --strict --esModuleInterop --skipLibCheck",
+    "test": "npm run build && npm run build:test && node dist/init.test.js && node --test scripts/release.test.js && node scripts/check-prose.js && node scripts/check-gotcha-tags.js && node scripts/generate-docs-index.js --check",
+    "prepack": "npm run build && node scripts/readme-links.js --publish",
+    "postpack": "node scripts/readme-links.js --restore && node -e \"const fs=require('fs');const version=process.env.npm_package_version;const scoped=process.env.npm_package_name.replace(/^@/,'').replace('/','-')+'-'+version+'.tgz';const unscoped=process.env.npm_package_name.replace(/^@[^/]+\\//,'')+'-'+version+'.tgz';if(scoped!==unscoped&&fs.existsSync(scoped))fs.renameSync(scoped,unscoped);\"",
+    "lint:prose": "node scripts/check-prose.js",
+    "lint:gotchas": "node scripts/check-gotcha-tags.js",
+    "docs:generate": "node scripts/generate-docs-index.js",
+    "release:prepare": "node scripts/release.js prepare"
+  },
+  "author": "Sam Wallace",
+  "license": "ISC",
+  "repository": {
+    "type": "git",
+    "url": "git+https://github.com/esko-bv/enf-switch-scripting-context.git"
+  },
+  "publishConfig": {
+    "registry": "https://registry.npmjs.org/",
+    "access": "public"
+  },
+  "devDependencies": {
+    "@types/node": "^20.0.0",
+    "typescript": "^5.0.0"
+  },
+  "homepage": "https://github.com/esko-bv/enf-switch-scripting-context#readme",
+  "bugs": {
+    "url": "https://github.com/esko-bv/enf-switch-scripting-context/issues"
+  },
+  "engines": {
+    "node": ">=18"
+  }
+}