Split out from #57 (§5, remaining sub-item).
Get started on your computer jumps straight from the intro into 1. Install, with no prerequisites section and no mention of the required Node version. A reader on Node 22.13 following it verbatim hits Unknown file extension ".ts" because Node only strips TypeScript types from 22.18 onward.
The two behavioural halves of that trap are already fixed: varar init now sets "type": "module", and varar run prints the exact fix for both the unknown-extension and the "import outside a module" failures. What is still missing is the doc side the issue asked for: state the Node baseline up front so a reader knows what they need before they start.
Suggested change
Add a short Prerequisites block (or <Aside>) before step 1 of tutorials/get-started.mdx:
- Node.js ≥ 22.18 for the TypeScript port (type stripping is on by default there; older Node needs
NODE_OPTIONS=--experimental-strip-types).
- Each other language needs its own toolchain (link out as appropriate).
Keep it to the TypeScript tab's reality — the JVM/Python/Ruby tabs have their own runtimes.
Split out from #57 (§5, remaining sub-item).
Get started on your computer jumps straight from the intro into 1. Install, with no prerequisites section and no mention of the required Node version. A reader on Node 22.13 following it verbatim hits
Unknown file extension ".ts"because Node only strips TypeScript types from 22.18 onward.The two behavioural halves of that trap are already fixed:
varar initnow sets"type": "module", andvarar runprints the exact fix for both the unknown-extension and the "import outside a module" failures. What is still missing is the doc side the issue asked for: state the Node baseline up front so a reader knows what they need before they start.Suggested change
Add a short Prerequisites block (or
<Aside>) before step 1 oftutorials/get-started.mdx:NODE_OPTIONS=--experimental-strip-types).Keep it to the TypeScript tab's reality — the JVM/Python/Ruby tabs have their own runtimes.