proposal-import-attributes

Proposal for syntax to import ES modules with assertions (by tc39)

Proposal-import-attributes Alternatives

Similar projects and alternatives to proposal-import-attributes

tc39
proposal-import-attributes
NOTE: The number of mentions on this list indicates mentions on common posts plus user suggested alternatives. Hence, a higher number means a better proposal-import-attributes alternative or higher similarity.

proposal-import-attributes discussion

Log in or Post with

proposal-import-attributes reviews and mentions

Posts with mentions or reviews of proposal-import-attributes. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2024-05-25.
  • The long path of JavaScript - from ES6 until today.
    4 projects | dev.to | 25 May 2024
    The proposal for import attributes aims to improve the import statement in JavaScript by allowing developers to assert certain conditions about the imported module. This can help catch errors at compile-time instead of runtime and make the code more robust. Currently this proposal is in Stage 3.
  • Power of Partial Prerendering with Bun
    2 projects | dev.to | 24 Mar 2024
    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
    1 project | dev.to | 9 Jan 2024
    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?
    2 projects | /r/css | 7 Dec 2023
    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?
    12 projects | news.ycombinator.com | 2 Aug 2023
    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
    2 projects | /r/webdev | 24 Jun 2023
    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?
    5 projects | dev.to | 22 May 2023
  • The Cost of Convenience
    2 projects | dev.to | 4 May 2023
    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
    7 projects | dev.to | 23 Mar 2023
    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 | 15 Jul 2024
    SaaSHub helps you find the best software and product alternatives Learn more →

Stats

Basic proposal-import-attributes repo stats
9
564
5.9
11 days ago

Sponsored
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.
www.influxdata.com

Did you konow that HTML is
the 11th most popular programming language
based on number of metions?