types-in-js
proposal-error-cause
types-in-js | proposal-error-cause | |
---|---|---|
3 | 6 | |
245 | 334 | |
- | - | |
4.3 | 5.7 | |
3 months ago | over 2 years ago | |
HTML | ||
Creative Commons Zero v1.0 Universal | 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.
types-in-js
-
TypeScript 5.0 for JavaScript devs
Head on over to voxpelli/types-in-js and read more about using types in JS and share your favorite additions lately 🙏
-
TypeScript 4.5 adds JSDoc template tag defaults
TypeScript 4.5, which is currently a release candidate, includes an exciting new feature for us types in js JSDoc users:
-
Pony Cause 1.0: Error Causes
Pony Cause is written in JS, typed with JSDoc, validated with TypeScript and have .d.ts / .d.ts.map generated by TypeScript. In other words: 100% typed in true Types in JS spirit.
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?
pony-cause - Ponyfill and helpers for the standardized Error Causes
proposal-intl-segmenter - Unicode text segmentation for ECMAScript
revanced-discussions - 💡 Discussions repository for ReVanced
proposal-temporal - Provides standard objects and functions for working with dates and times.
proposals - ✍️ Tracking the status of Babel's implementation of TC39 proposals (may be out of date)
proposal-resizablearraybuffer - Proposal for resizable array buffers
proposal-string-dedent - TC39 Proposal to remove common leading indentation from multiline template strings
proposal-deiter - Double-Ended Iterator and Destructuring
proposal-integer-and-modulus-math - Proposal for additional static methods on Math
effect - An ecosystem of tools to build robust applications in TypeScript.
proposal-module-declarations - JavaScript Module Declarations