proposal-static-class-features
The static parts of new class features, in a separate proposal (by tc39)
proposal-private-fields-in-in
EcmaScript proposal to provide brand checks without exceptions (by tc39)
| proposal-static-class-features | proposal-private-fields-in-in | |
|---|---|---|
| 3 | 3 | |
| 130 | 29 | |
| - | - | |
| 0.8 | 2.8 | |
| over 2 years ago | almost 3 years ago | |
| HTML | HTML | |
| - | MIT License |
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
proposal-static-class-features
Posts with mentions or reviews of proposal-static-class-features.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2021-04-01.
-
Tree shaking for JavaScript library authors
I’ll illustrate, what I mean, with a simple class having a static field. (Static class fields will become an official part of the language with the upcoming ES2021 specification, but they are already widely used by developers.)
-
log
This is not currently true. But there are proposals, currently in stage 3 for allowing this.
-
What is the current state of private fields in ES6 classes?
Static class fields and private static methods
proposal-private-fields-in-in
Posts with mentions or reviews of proposal-private-fields-in-in.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2021-04-13.
-
JS classes are not “just syntactic sugar”
I believe this was true, but it is becoming increasingly untrue as the spec gives more and more abilities and semantics to classes. Like, as you say, private fields, and more on the way.
-
What is the current state of private fields in ES6 classes?
Ergonomic brand checks for Private Fields
-
Updates from 80th TC39 meeting
Ergonomic Brand Checks for Private Fields: Check if an object has a private field, and if not, have some fallback behavior.
What are some alternatives?
When comparing proposal-static-class-features and proposal-private-fields-in-in you can also consider the following projects:
proposal-private-declarations - A proposal to allow trusted code _outside_ of the class lexical scope to access private state
proposal-intl-DateTimeFormat-formatRange - ECMA 402 proposal for DateTimeFormat.prototype.{formatRange,formatRangeToParts}
proposal-class-fields - Orthogonally-informed combination of public and private fields proposals
proposal-class-brand-check - JavaScript proposal to provide class brand checks
proposal-private-methods - Private methods and getter/setters for ES6 classes
proposal-json-modules - Proposal to import JSON files as modules
proposal-static-class-features vs proposal-private-declarations
proposal-private-fields-in-in vs proposal-intl-DateTimeFormat-formatRange
proposal-static-class-features vs proposal-class-fields
proposal-private-fields-in-in vs proposal-class-brand-check
proposal-static-class-features vs proposal-private-methods
proposal-private-fields-in-in vs proposal-private-methods
proposal-private-fields-in-in vs proposal-json-modules
proposal-private-fields-in-in vs proposal-class-fields