proposal-intl-locale-info
proposal-error-cause
| proposal-intl-locale-info | proposal-error-cause | |
|---|---|---|
| 3 | 6 | |
| 49 | 334 | |
| - | - | |
| 6.6 | 5.7 | |
| 4 months ago | over 2 years ago | |
| HTML | HTML | |
| MIT License | MIT License |
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-intl-locale-info
-
Updates from 82nd meeting of TC39
Intl Locale Info API part of ECMA402: A proposal to expose Locale information, such as week data (first day in a week, weekend start day, weekend end day, minimun day in the first week), and text direction hour cycle used in the locale.
-
Updates from 80th TC39 meeting
Intl.DisplayNames: enable developers to get translation of language, region or script display names on the client, part of ECMA-402.
-
Updates from 78th meeting of TC39
Intl Locale Info
proposal-error-cause
-
GraphQL error handling to the max with Typescript, codegen and fp-ts
:::note When using remote APIs, we often have the possibility to generate the types automatically from a JSON schema for REST APIs, from protobuf files for gRPC-based APIs, from a database schema, etc. You might even be using an external API through an SDK that already provides you with all types. In such cases, the creation of specialized Error classes is not mandatory. However, it might still be a good idea to do so to provide application-specific errors rather than bubbling up 3rd-party low-level errors. For such cases, the upcoming Ecma TC39 proposal for Error Cause is useful as it allows to chain errors. Polyfills exist: Pony Cause or error-cause. :::
-
Updates from the 86th meeting of TC39
Error Cause : .cause property on all Error types slides.
-
Pony Cause 1.0: Error Causes
The impact and cause provides the most value when paired with the other, and that's what Error Cause enables and what Pony Cause is is a ponyfill for and provides helpers for.
-
Error Cause in JavaScript
Well, we have error-cause on stage-3 for the same and with which we could do something like:
-
Updates from the 81st meeting of TC39
Error Cause: Enhancing errors with a distinct "cause".
-
Updates from 78th meeting of TC39
Error Cause
What are some alternatives?
proposal-intl-enumeration - Return supported values of options, such as timeZone, calendars, numberingSystems, currencies, units
proposal-intl-segmenter - Unicode text segmentation for ECMAScript
proposal-json-modules - Proposal to import JSON files as modules
proposal-temporal - Provides standard objects and functions for working with dates and times.
proposal-class-static-block - ECMAScript class static initialization blocks
pony-cause - Ponyfill and helpers for the standardized Error Causes
proposal-array-find-from-last - Proposal for Array.prototype.findLast and Array.prototype.findLastIndex.
proposals - ✍️ Tracking the status of Babel's implementation of TC39 proposals (may be out of date)
proposal-string-dedent - TC39 Proposal to remove common leading indentation from multiline template strings
types-in-js - Tips and tricks for working with types in JavaScript
proposal-intl-DateTimeFormat-formatRange - ECMA 402 proposal for DateTimeFormat.prototype.{formatRange,formatRangeToParts}
proposal-resizablearraybuffer - Proposal for resizable array buffers