proposal-resizablearraybuffer
proposal-error-cause
| proposal-resizablearraybuffer | proposal-error-cause | |
|---|---|---|
| 6 | 6 | |
| 157 | 334 | |
| - | - | |
| 0.0 | 5.7 | |
| almost 2 years ago | almost 4 years ago | |
| HTML | HTML | |
| - | 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-resizablearraybuffer
-
Goodbye, Node.js Buffer
Nit: "fixed-length" is no longer true as of very recently [1].
[1] https://github.com/tc39/proposal-resizablearraybuffer
-
Updates from the 98th TC39 meeting
Resizable ArrayBuffer: Resizable and growable ArrayBuffers.
-
What Is The Importance Of A Buffer Size in .alloc()?
Stage 3 Draft linked above https://tc39.es/proposal-resizablearraybuffer/. Implemented in Chrome and Chromium.
-
Deno Joins TC39
This is a great news! Good luck, Luca!
> Better support for explicit resource management
+1
Since everyone is making feature requests, I'd like to point out `ArrayBuffer.transfer`[1] -- ability to effectively move data without copying would do wonders for low-level/high-performance code in JS.
[1] https://github.com/tc39/proposal-resizablearraybuffer
-
Updates from 78th meeting of TC39
Resizable ArrayBuffers
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?
nodejs-polars - nodejs front-end of polars
proposal-module-declarations - JavaScript Module Declarations
simpatico - Simpatico is an umbrella term for several data-structures and algorithms written in JavaScript
proposal-string-dedent - TC39 Proposal to remove common leading indentation from multiline template strings
proposal-class-static-block - ECMAScript class static initialization blocks
proposal-intl-segmenter - Unicode text segmentation for ECMAScript