uibuilder
proposal-import-attributes
uibuilder | proposal-import-attributes | |
---|---|---|
6 | 8 | |
128 | 544 | |
- | 2.4% | |
0.0 | 5.9 | |
about 4 years ago | 3 months ago | |
TypeScript | HTML | |
MIT License | Apache License 2.0 |
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.
uibuilder
- Web Components Will Outlive Your JavaScript Framework
- If Web Components are so great, why am I not using them?
- Ask HN: Good resource on writing web app with plain JavaScript/HTML/CSS
-
AlpineJS – Lightweight JavaScript Framework
This looks bad. I see custom syntax, and JavaScript embedded into HTML in a way that cannot be syntax-checked at build time.
If you want a lightweight framework check out UIBuilder instead: https://github.com/wisercoder/uibuilder
Same JSX syntax as React, but this lib is very simple -- just over 200 lines of source code.
-
Virtual DOM is pure overhead
If you don't need Virtual DOM then Web Components are a great idea for building reusable components that work with all frameworks, including React. You can even use JSX to build Web Components: https://github.com/wisercoder/uibuilder
proposal-import-attributes
-
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
What are some alternatives?
svelte-query - Performant and powerful remote data synchronization for Svelte
proposal-class-method-parameter-decorators - Decorators for ECMAScript class method and constructor parameters
react-svelte - Use Svelte components inside a React app
unpkg - The CDN for everything on npm
Alpine.js - A rugged, minimal framework for composing JavaScript behavior in your markup.
proposal-float16array - a proposal to add float16 TypedArrays to JavaScript
budibase - Budibase is an open-source low code platform that helps you build internal tools in minutes 🚀
proposal-await-dictionary - A proposal to add Promise.ownProperties(), Promise.fromEntries() to ECMAScript
fastdom - Eliminates layout thrashing by batching DOM measurement and mutation tasks
custom-elements - Using custom elements
yhtml - Tiny html tag function for rendering Web Component templates with event binding