From bbd1fa5e2f7fa127e865ad84c389e3f4bc02d537 Mon Sep 17 00:00:00 2001 From: Muhammad Salman Aziz <85288719+salman-aziz-4425@users.noreply.github.com> Date: Sun, 19 Oct 2025 13:34:28 +0500 Subject: [PATCH] doc: update decorator documentation to reflect actual policy - Remove misleading 'soon' language - Remove 'temporary limitation' claim - Clarify that Node.js will not provide polyfills - Wait for native JavaScript engine support Refs: https://github.com/nodejs/node/issues/60282 PR-URL: https://github.com/nodejs/node/pull/60288 Reviewed-By: Marco Ippolito Reviewed-By: Jacob Smith Reviewed-By: Richard Lau Reviewed-By: Colin Ihrig Reviewed-By: Geoffrey Booth --- doc/api/typescript.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/doc/api/typescript.md b/doc/api/typescript.md index 158a55ea12..b5b7017d5e 100644 --- a/doc/api/typescript.md +++ b/doc/api/typescript.md @@ -158,10 +158,10 @@ namespace A { } ``` -Since Decorators are currently a [TC39 Stage 3 proposal](https://github.com/tc39/proposal-decorators) -and will soon be supported by the JavaScript engine, +Since Decorators are currently a [TC39 Stage 3 proposal](https://github.com/tc39/proposal-decorators), they are not transformed and will result in a parser error. -This is a temporary limitation and will be resolved in the future. +Node.js does not provide polyfills and thus will not support decorators until +they are supported natively in JavaScript. In addition, Node.js does not read `tsconfig.json` files and does not support features that depend on settings within `tsconfig.json`, such as paths or