proposal-json-parse-with-source
Proposal for extending JSON.parse to expose input source text. (by tc39)
proposal-faster-promise-adoption
Reduce the number of microtask ticks required to adopt the state of a promise (by tc39)
proposal-json-parse-with-source | proposal-faster-promise-adoption | |
---|---|---|
2 | 1 | |
208 | 45 | |
2.4% | - | |
5.5 | 4.1 | |
8 months ago | almost 2 years ago | |
HTML | HTML | |
MIT License | 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-json-parse-with-source
Posts with mentions or reviews of proposal-json-parse-with-source.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2022-06-09.
-
Why does JSON.parse corrupt large numbers and how to solve this?
And my point is that you can, you just need to, like the article says, use a library that supports it. No need to store the number as a string. Hell, the article even links to a proposal to update JSON.parse to be able to handle it.
-
Updates from the 90th TC39 meeting
JSON.parse source text access: Extending JSON.parse to expose input source text.
proposal-faster-promise-adoption
Posts with mentions or reviews of proposal-faster-promise-adoption.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2022-06-09.
-
Updates from the 90th TC39 meeting
Symbols as WeakMap keys: Permit Symbols as keys in WeakMaps, entries in WeakSets and WeakRefs, and registered in FinalizationRegistries
What are some alternatives?
When comparing proposal-json-parse-with-source and proposal-faster-promise-adoption you can also consider the following projects:
proposal-string-dedent - TC39 Proposal to remove common leading indentation from multiline template strings
proposal-regexp-atomic-operators