proposal-private-fields-in-in
EcmaScript proposal to provide brand checks without exceptions (by tc39)
proposal-regexp-legacy-features
Legacy static properties of the RegExp constructor in JavaScript (by tc39)
| proposal-private-fields-in-in | proposal-regexp-legacy-features | |
|---|---|---|
| 3 | 1 | |
| 29 | 40 | |
| - | - | |
| 2.8 | 0.0 | |
| almost 3 years ago | 7 months ago | |
| HTML | ||
| MIT License | Creative Commons Zero v1.0 Universal |
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-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.
proposal-regexp-legacy-features
Posts with mentions or reviews of proposal-regexp-legacy-features.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2021-01-28.
-
Updates from 80th TC39 meeting
regex-set-notation: Adopting Unicode behavior for set notation in regular expressions.
What are some alternatives?
When comparing proposal-private-fields-in-in and proposal-regexp-legacy-features you can also consider the following projects:
proposal-intl-DateTimeFormat-formatRange - ECMA 402 proposal for DateTimeFormat.prototype.{formatRange,formatRangeToParts}
proposal-json-modules - Proposal to import JSON files as modules
proposal-class-brand-check - JavaScript proposal to provide class brand checks
proposal-array-find-from-last - Proposal for Array.prototype.findLast and Array.prototype.findLastIndex.
proposal-private-methods - Private methods and getter/setters for ES6 classes
proposal-intl-extend-timezonename - Extend TimeZoneName Option Proposal
proposal-class-fields - Orthogonally-informed combination of public and private fields proposals
proposal-private-fields-in-in vs proposal-intl-DateTimeFormat-formatRange
proposal-regexp-legacy-features vs proposal-json-modules
proposal-private-fields-in-in vs proposal-class-brand-check
proposal-regexp-legacy-features vs proposal-array-find-from-last
proposal-private-fields-in-in vs proposal-private-methods
proposal-regexp-legacy-features vs proposal-intl-extend-timezonename
proposal-private-fields-in-in vs proposal-json-modules
proposal-private-fields-in-in vs proposal-class-fields