proposal-private-fields-in-in
EcmaScript proposal to provide brand checks without exceptions (by tc39)
RegExp.escape
Proposal for investigating RegExp escaping for the ECMAScript standard (by benjamingr)
| proposal-private-fields-in-in | RegExp.escape | |
|---|---|---|
| 3 | 3 | |
| 29 | 328 | |
| - | 2.7% | |
| 2.8 | 7.3 | |
| almost 3 years ago | 30 days ago | |
| HTML | JavaScript | |
| 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.
RegExp.escape
Posts with mentions or reviews of RegExp.escape.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2023-09-29.
-
Updates from the 98th TC39 meeting
RegExp.escape: Proposal for investigating RegExp escaping for the ECMAScript standard.
- Why is there no regex escape function in JavaScript? It was vetoed by one person
-
Updates from 80th TC39 meeting
Escaping Strings for RegExps: escaping a string for use inside a Regular Expression.
What are some alternatives?
When comparing proposal-private-fields-in-in and RegExp.escape you can also consider the following projects:
proposal-intl-DateTimeFormat-formatRange - ECMA 402 proposal for DateTimeFormat.prototype.{formatRange,formatRangeToParts}
proposal-class-brand-check - JavaScript proposal to provide class brand checks
proposal-intl-extend-timezonename - Extend TimeZoneName Option Proposal
proposal-private-methods - Private methods and getter/setters for ES6 classes
proposal-resizablearraybuffer - Proposal for resizable array buffers
proposal-json-modules - Proposal to import JSON files as modules
proposal-class-fields - Orthogonally-informed combination of public and private fields proposals
proposal-intl-localematcher - Proposal for Intl.LocaleMatcher
proposal-private-fields-in-in vs proposal-intl-DateTimeFormat-formatRange
RegExp.escape vs proposal-intl-DateTimeFormat-formatRange
proposal-private-fields-in-in vs proposal-class-brand-check
RegExp.escape vs proposal-intl-extend-timezonename
proposal-private-fields-in-in vs proposal-private-methods
RegExp.escape vs proposal-resizablearraybuffer
proposal-private-fields-in-in vs proposal-json-modules
RegExp.escape vs proposal-class-brand-check
proposal-private-fields-in-in vs proposal-class-fields
RegExp.escape vs proposal-intl-localematcher