N/M Quantum Language for VS Code

Write, test and debug N/M quantum programs with local simulation. Publisher: QuantumSoftware · Extension ID: quantumsoftware.nm-quantum-language.

Türkçe kullanım rehberi · Explore N/M · Report an issue

Version 0.2.1 is available on the regular Marketplace release channel. The N/M toolchain remains at preview maturity and uses a local simulator. It does not submit jobs to physical quantum hardware or demonstrate quantum advantage.

Get started

1. Install N/M Quantum Language by QuantumSoftware using Install in VS Code. A downloaded VSIX can also be installed with Extensions: Install from VSIX....
2. Open a project you trust. Run N/M: Create Quantum Example from the Command Palette.
3. Run N/M: Run Current File Tests. The example prepares a balanced qubit and checks both probabilities in the local simulator.
4. Save as hello.nm, then explore completion, hover, Go to Definition, Find References, Rename and Format Document.
5. Use N/M: Show Capability Status to check feature maturity and limits.

Features

• Syntax and semantic highlighting, diagnostics, completion, hover and signature help for .nm files.
• Definitions, references, scoped rename, document/range formatting, quick fixes, symbols, folding and inlay hints.
• Recorded debugging with source breakpoints, step in/over/out, call stack, typed variables and replay restart.
• Test Explorer for open N/M documents. Closing a file removes its discovered checks. Selecting one check executes the document and shows selected results.
• Import-aware workspace indexing. Each nm-workspace.json applies to its own subtree; the nearest manifest wins.
• English/Turkish commands, settings and extension messages. Compiler diagnostics and source identifiers retain language-service wording.

Language profile and settings

New installations enable six parts of the default N/M profile: classicalFunctions, typedClassicalValues, functionResults, moduleVisibility, parameterGroups and computeApply. Previously saved false choices remain off. Other nm.experimental.* settings remain off by default. Preview/experimental limitations still apply; consult N/M: Show Capability Status before use.

The VSIX includes its language server and debug runtime. Desktop VS Code needs no separate Node.js installation. nm.languageServer.path accepts an existing absolute file path for a custom server. An invalid explicit path produces an error rather than silently selecting another server.

N/M settings changes restart the server and reopen documents automatically. If it fails, click the N/M status item or run N/M: Restart Language Server. Details appear in Output > N/M Language.

Tests run in separate cancellable processes. Test requests time out after 60 seconds; normal server requests after 15 seconds. Indexing is bounded to 5,000 source files, 100 manifests, 1 MB per file and 5 MB total source. The JSON transport has a separate 8 MB limit. Incomplete indexing produces a warning; aggregate limits preserve the previous index.

Restricted Mode and virtual workspaces are unsupported. Workspace trust is required before the server or tests run. Desktop and remote Node extension hosts are supported; this is not a browser-only extension.

Guides

• Recorded debugger
• Float math
• Angle units
• Parameter groups
• Compute/apply

License

Free to install and use for personal, educational and commercial purposes. QuantumSoftware retains rights to its code and assets; modifying or redistributing them requires separate permission, subject to applicable law and third-party licenses. Your N/M programs and simulation results are not restricted by this license. See the packaged LICENSE.txt and Marketplace License link. This is not an open-source license.

Build and verification

From the repository root, use its pinned Node.js/npm versions:

npm ci
npm run test:nm:vscode
npm run package:nm-vscode
npm run test:nm:vscode-host

The host runner installs the actual VSIX into an isolated profile without changing personal extensions. The VS Code version is pinned in config/nm-vscode-host.json. Packages are under .nm-package-build; reports under .vscode-test/reports. Local tests do not establish Marketplace status.