SaaSHub helps you find the best software and product alternatives Learn more →
Proposal-import-attributes Alternatives
Similar projects and alternatives to proposal-import-attributes
-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
-
stencil
A toolchain for building scalable, enterprise-ready component systems on top of TypeScript and Web Component standards. Stencil components can be distributed natively to React, Angular, Vue, and traditional web developers from a single, framework-agnostic codebase.
-
SaaSHub
SaaSHub - Software Alternatives and Reviews. SaaSHub helps you find the best software and product alternatives
-
proposal-class-method-parameter-decorators
Decorators for ECMAScript class method and constructor parameters
-
proposal-await-dictionary
A proposal to add Promise.ownProperties(), Promise.fromEntries() to ECMAScript
-
proposal-canonical-tz
TC39 Proposal (stacked on Temporal) to improve handling of changes to the IANA Time Zone Database
-
SaaSHub
SaaSHub - Software Alternatives and Reviews. SaaSHub helps you find the best software and product alternatives
proposal-import-attributes reviews and mentions
-
Power of Partial Prerendering with Bun
Bun introduces the idea of Macros into JavaScript. Macros are a new paradigm that allows optimizations ahead of time just by adding an import attribute.
-
How to use import attributes in TypeScript and JavaScript
TypeScript v5.3 builds on its JavaScript foundation by adding import attributes with the usual type safety and tooling benefits inherent to the language. You can follow the TypeScript proposal for import attributes on GitHub.
-
CSS Modules Still a Thing?
Yup, in vanilla that's fine, but I'm not sure whether bundlers etc are able to understand import assertions yet, as the spec is still being finalised - for example: the 'assert' keyword has now been officially changed to 'with', but only 'assert' is implemented anywhere at the moment.
-
If Web Components are so great, why am I not using them?
Things like HTML (and JSON) imports in ES modules, among other things, have been waiting on some safety signalling mechanics currently named "Import Attributes". Import Attributes are currently in Stage 3 [0].
The basic security story is that browsers never care about file extensions, they care about MIME types. A developer might add an import to a third-party HTML or JSON file somewhere and expect one "safe" behavior, but the third-party could just return a MIME type of "text/javascript" and inject an entire script and the browser is supposed to respect that MIME type.
To keep things safe, browsers want a way to signal that an import is supposed to JSON (or HTML or CSS) rather than JS and error if it gets back something "wrong" from a server request. That's one of the proposed uses for Import Attributes to suggest expected MIME types for non-JS modules in ES module imports.
Unfortunately, there are other proposed uses for Import Attributes (things like including hashes for integrity checks) and so there have been quite a few revisions (and multiple names) for Import Attributes trying to best support as many of the proposed uses as possible, and that has slowed progress on it a lot more than some people would wish.
[0] https://github.com/tc39/proposal-import-attributes
-
[Showoff Saturday] Replacing Abandoned Dependencies
This was an idea that I came up with when thinking about how to handle import styles from './styles.css' with { type: 'css' } in @shgysk8zer0/rollup-import. Import assertions / import attributes are now back to stage 3, but only JSON is actually progressing. So I decided to wait until there's a stable spec.
- Rails Frontend Bundling - Which one should I choose?
-
The Cost of Convenience
None of these examples will actually work in a browser, because they are non-standard. Some of you might have correctly spotted that a browser standard exists for two of the imports pointed out in the example, namely the Import Attributes proposal (previously known as Import Assertions), but these imports in their current shape will not work natively in a browser. Many of these non-standard imports exist for good reason; they are very convenient.
-
Updates from the 95th TC39 meeting
import attribute: Import Assertions re-adanced to Stage-3. Proposal for syntax to import ES modules with assertions
-
A note from our sponsor - SaaSHub
www.saashub.com | 5 May 2024
Stats
tc39/proposal-import-attributes is an open source project licensed under Apache License 2.0 which is an OSI approved license.
The primary programming language of proposal-import-attributes is HTML.
Popular Comparisons
- proposal-import-attributes VS proposal-class-method-parameter-decorators
- proposal-import-attributes VS unpkg
- proposal-import-attributes VS proposal-float16array
- proposal-import-attributes VS proposal-await-dictionary
- proposal-import-attributes VS uibuilder
- proposal-import-attributes VS custom-elements
- proposal-import-attributes VS yhtml
- proposal-import-attributes VS vite_ruby
- proposal-import-attributes VS fastdom
- proposal-import-attributes VS custom-elements-everywhere
Sponsored