I dati tecnici e le note di misurazione sono mantenuti in inglese per evitare discrepanze tra le traduzioni.

Roadmap

A current status page, not a frozen release history. Exact support lives in the linked platform, limitations, benchmark, and changelog sources.

Verified today

✓SWC parsing and LLVM ahead-of-time code generation for native TypeScript and JavaScript builds.
✓About 97% of the tracked Node suite across 53 modules, plus roughly 50 native package/API implementations.
✓Eleven documented targets: macOS, iOS, iPadOS, visionOS, tvOS, watchOS, Android, Wear OS, Windows, Linux, and Web/WASM.
✓Web and WASM are aliases for one backend; HarmonyOS is a separate preview.
✓The perry compile, run, check, doctor, verify, and publish command surfaces are present in the current CLI.

→Closing TypeScript, JavaScript, Node.js, npm-package, Proxy, decorator, weak-reference, and dynamic-code compatibility gaps.
→Improving platform parity, especially core and preview targets.
→GC, representation selection, dynamic dispatch, startup, binary size, and realistic workload performance.
→Hosted build, signing, verification, and distribution operations; public availability and terms are confirmed separately from compiler support.

·Current pages use generated facts for target counts and benchmark rows instead of copying numbers into multiple components.
·Historic blog posts keep their date and version context and are not presented as current benchmarks.
·Support means documented, tested behavior — not blanket compatibility with every TypeScript program or npm package.
·Exact prices, quotas, SLAs, and hosted-service availability are not promised until they are confirmed in the service or a signed agreement.

Perry is pre-1.0 and changes quickly. Use these live sources when making a technical or commercial decision.