System requirements
These requirements describe the 0.1.0 test version (c657e568). WworPoint runs on your computer. This website provides documentation; it is not the document editor.
Start with the VS Code extension
Section titled “Start with the VS Code extension”| You need | What to check |
|---|---|
| Desktop VS Code | Version 1.101 or later. The extension includes its document engine and uses VS Code’s runtime. No separate Node.js, npm or globally installed CLI is needed. |
| A locally installed browser | Google Chrome, Microsoft Edge or Chromium 154 or later. WworPoint does not download one. It uses the local browser for layout validation, PDF/HTML export and Mermaid diagrams. |
| A local project folder | Choose a folder you can write to and have created or reviewed. WworPoint saves project files, temporary generated files and exports there. |
| Workspace trust | Required for layout validation, export and diagram/chart rendering, including Mermaid and Vega-Lite. Restricted Mode can preview sources but does not enable these operations. Trust only folders whose contents you understand. |
Operating systems and verification
Section titled “Operating systems and verification”Browser discovery is implemented for Windows, macOS and Linux. That describes the implementation, not complete UI verification on every system.
- macOS: the current named 0.1.0 test packages were verified on macOS 26.6.2 with VS Code 1.139.1 and Chrome/Edge 154, including installed extension and CLI exports.
- Linux: earlier browser and preview tests exist; complete current-version UI verification is not established here.
- Windows: executable discovery has automated tests; full current-version UI verification is not established here.
Use desktop VS Code with a local folder for this guide. VS Code for the Web and virtual workspaces are unsupported. Remote SSH, WSL and Dev Containers are not verified by this guide; do not assume a browser on your own desktop is available to a remote extension host.
No product-specific minimum RAM or free disk capacity has been established. Keep enough writable space for your source files, images and exports; larger documents may need more resources.
A quick environment check
Section titled “A quick environment check”- Check the version in VS Code’s About dialog and your browser’s About page.
- Open your own local folder in VS Code and confirm you can save a file there.
- Install the supplied test VSIX using the installation guide. Review the folder before enabling Workspace Trust.
- Run WworPoint: Init, then WworPoint: Preview. Save your document and run WworPoint: Validate, then WworPoint: Export. Confirm the exported PDF opens.
| If something does not work | Try this |
|---|---|
| Browser not found or too old | Install/update a listed browser. If detection still fails, set wworpoint.browserPath to its executable’s absolute path in a trusted workspace. |
| Export or diagrams/charts are unavailable | Check Workspace Trust and the Problems panel. Review the folder before trusting it. |
| Files cannot be saved | Move your reviewed project to a local folder you can write to, then reopen it. |
| Layout findings block export | Read the Problems panel, correct the document and save it, then validate again. |
CLI is optional and advanced
Section titled “CLI is optional and advanced”Only the separately installed CLI requires Node.js 22.12 or later. Check with node --version. The same installed browser and writable project-folder requirements apply. See CLI installation; the test package is not yet published to npm.
AI and network access
Section titled “AI and network access”AI is optional and separate. WworPoint includes no model, built-in AI integration or credits. If you choose an external AI service/tool, its account requirements, network access, fees and data-handling terms apply. AI processing is not necessarily local. Normal WworPoint preview, validation and export run locally; VS Code, browsers and external AI tools have their own network behavior.