proposal-import-assertions
proposal-error-cause
proposal-import-assertions | proposal-error-cause | |
---|---|---|
15 | 6 | |
390 | 334 | |
- | - | |
0.0 | 5.7 | |
about 1 year ago | over 2 years ago | |
HTML | HTML | |
Apache License 2.0 | 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-import-assertions
-
First use of Web-pack review: Restaurant page
SO, you're using webpack to support CSS imports here, BUT, did you know that you can do this in vanilla JS without webpack using something called import assertions:
-
Show HN: Deon.land – Deno.land?
This could be implemented as an import assertion[1]:
import foo from 'http://example.com/foo' assert { sha256sum: '...' }
This feature would even be useful in the web platform in general. Along with an assertion for importing plain text files (not just JSON files).
[1]: https://github.com/tc39/proposal-import-assertions
-
Updates from the 94th TC39 meeting
Worth noting that Import Assertions were downgraded to stage 2 from stage 3. The proposal page may continue to say "stage 3" until it can be updated.
Import Assertions: Proposal for syntax to import ES modules with assertions
-
Ideas For A Javascript Stricter Mode
Also, I'm not sure how that'd work with import assertions. That'd add another round of questions.
-
How to import text files like .css or .txt on Deno?
Hi, there is a way to import json file like:
-
You can import non-JS files into JavaScript without bundlers & loaders
If you want the real thing, you're looking for import assertions.
-
NPM changes image path??..
But it's still only a proposal, currently at stage 3 (which means it's almost finalised, pending any critical feedback or refinements, before it gets implemented). You can view the import assertions proposal on GitHub.
-
Import Assertion support on Safari?
I wouldn't use import assertions in any browser since they are still a stage 3 proposal so any browser which implements them is doing before it is standardized and shouldn't be relied upon for anything that matters.
-
Deno Joins TC39
There's an issue for that to be added as aprt of import assertions https://github.com/tc39/proposal-import-assertions/issues/11...
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-pattern-matching - Pattern matching syntax for ECMAScript
proposal-intl-segmenter - Unicode text segmentation for ECMAScript
proposal-source-phase-imports - Proposal to enable importing modules at the source phase
proposal-temporal - Provides standard objects and functions for working with dates and times.
WHATWG HTML Standard - HTML Standard
pony-cause - Ponyfill and helpers for the standardized Error Causes
proposal-symbols-as-weakmap-keys - Permit Symbols as keys in WeakMaps, entries in WeakSets and WeakRefs, and registered in FinalizationRegistries
proposals - ✍️ Tracking the status of Babel's implementation of TC39 proposals (may be out of date)
proposal-pipeline-operator - A proposal for adding a useful pipe operator to JavaScript.
types-in-js - Tips and tricks for working with types in JavaScript
proposal-async-context - Async Context for JavaScript
proposal-resizablearraybuffer - Proposal for resizable array buffers