# Suggestion <!-- Please fill in each section completely. Thank you! --> ## 🔍 Search Terms <!-- 💡 Did you know? TypeScript has over 2,000 open suggestions! 🔎 Please search thoroughly before logging new feature requests as most common ideas already have a proposal in progress. The "Common Feature Requests" section of the FAQ lists many popular requests: https://github.com/Microsoft/TypeScript/wiki/FAQ#common-feature-requests Replace the text below: --> es2022, class field ## ✅ Viability Checklist <!-- Suggestions that don't meet all these criteria are very, very unlikely to be accepted. We always recommend reviewing the TypeScript design goals before investing time writing a proposal for ideas outside the scope of the project. --> My suggestion meets these guidelines: * [x] This wouldn't be a breaking change in existing TypeScript/JavaScript code * [x] This wouldn't change the runtime behavior of existing JavaScript code * [x] This could be implemented without emitting different JS based on the types of the expressions * [x] This isn't a runtime feature (e.g. library functionality, non-ECMAScript syntax with JavaScript output, new syntax sugar for JS, etc.) * [x] This feature would agree with the rest of [TypeScript's Design Goals](https://github.com/Microsoft/TypeScript/wiki/TypeScript-Design-Goals). ## ⭐ Suggestion <!-- A summary of what you'd like to see added or changed --> Emit class fields as-is with `target: es2022`. ## 📃 Motivating Example <!-- If you were announcing this feature in a blog post, what's a short explanation that shows a developer why this feature improves the language? --> Projects targeting es2022 can emit class fields as-is.
Suggestion
🔍 Search Terms
es2022, class field
✅ Viability Checklist
My suggestion meets these guidelines:
⭐ Suggestion
Emit class fields as-is with
target: es2022.📃 Motivating Example
Projects targeting es2022 can emit class fields as-is.