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 <marcoippolito54@gmail.com>
Reviewed-By: Jacob Smith <jacob@frende.me>
Reviewed-By: Richard Lau <richard.lau@ibm.com>
Reviewed-By: Colin Ihrig <cjihrig@gmail.com>
Reviewed-By: Geoffrey Booth <webadmin@geoffreybooth.com>
This commit is contained in:
Muhammad Salman Aziz 2025-10-19 13:34:28 +05:00 committed by GitHub
parent 481b9b11b3
commit bbd1fa5e2f
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194

View File

@ -158,10 +158,10 @@ namespace A {
} }
``` ```
Since Decorators are currently a [TC39 Stage 3 proposal](https://github.com/tc39/proposal-decorators) Since Decorators are currently a [TC39 Stage 3 proposal](https://github.com/tc39/proposal-decorators),
and will soon be supported by the JavaScript engine,
they are not transformed and will result in a parser error. 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 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 features that depend on settings within `tsconfig.json`, such as paths or