proposal-temporal
proposal-error-cause
Our great sponsors
proposal-temporal | proposal-error-cause | |
---|---|---|
90 | 6 | |
3,120 | 334 | |
2.8% | - | |
9.4 | 5.7 | |
8 days ago | over 2 years ago | |
HTML | HTML | |
GNU General Public License v3.0 or later | 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-temporal
- TC39 Temporal Proposal
- Handling Hindu Lunisidereal Calendars
- Replacing Date with Temporal – ECMAScript Stage 3 Proposal
- Temporal, a modern date/time API for ECMAScript
- Temporal proposal reaches stage 4
-
Show HN: Trigger.dev V2 – a Temporal alternative for TypeScript devs
In the TypeScript/JavaScript world the only thing called "Temporal" that I was aware of is the Stage 3 proposal for an excellent new date and time module:
https://tc39.es/proposal-temporal/docs/
-
Updates from the 97th TC39 meeting
Time Zone Canonicalization: Stacked on Temporal to improve handling of changes to the IANA Time Zone Database.
- IAMA senior javascript dev, ask me anything
-
What library do you use to handle dates?
Roll-on Temporal!
There is a list of polyfills at the bottom of the page that can be used in production. https://github.com/tc39/proposal-temporal
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?
moment - Parse, validate, manipulate, and display dates in javascript.
proposal-intl-segmenter - Unicode text segmentation for ECMAScript
dayjs - ⏰ Day.js 2kB immutable date-time library alternative to Moment.js with the same modern API
pony-cause - Ponyfill and helpers for the standardized Error Causes
Luxon - ⏱ A library for working with dates and times in JS
proposals - ✍️ Tracking the status of Babel's implementation of TC39 proposals (may be out of date)
date-fns - ⏳ Modern JavaScript date utility library ⌛️
types-in-js - Tips and tricks for working with types in JavaScript
You-Dont-Need-Momentjs - List of functions which you can use to replace moment.js + ESLint Plugin
proposal-resizablearraybuffer - Proposal for resizable array buffers
sdk-typescript - Temporal TypeScript SDK
proposal-string-dedent - TC39 Proposal to remove common leading indentation from multiline template strings