Re:Alpine.js: A minimal framework for composing JavaScript b...
by strogonoff on Tuesday February 11, 2020 @06:03AM
(#22297568)
I wish there was a single accepted standard for deploying native components. Last time I checked there were two competing implementations, JS modules (<script type="module" src="my-component.js">) and HTML imports (<link rel="import" href="my-component.html">, my personal favorite).
[ Parent
| on HN ]
Re:Alpine.js: A minimal framework for composing JavaScript b...
by spankalee on Tuesday February 11, 2020 @10:17PM
(#22305413)
HTML Imports are not standard and have been removed from Chrome. <script type="module" src="my-component.js"> is indeed the single accepted standard.
Re:Alpine.js: A minimal framework for composing JavaScript b...
by strogonoff on Wednesday February 12, 2020 @05:15AM
(#22307566)
The working draft was last updated in December 2019, unfortunate that browser support is so poor.
Re:Alpine.js: A minimal framework for composing JavaScript b...
by spankalee on Wednesday February 12, 2020 @05:25PM
(#22313484)
Browser support isn't poor, it's just not a thing anymore. Chrome removing HTML Imports in _good_ so that we can move on to an agreed upon replacement that integrates with the JS module system like HTML Modules.
Re:Alpine.js: A minimal framework for composing JavaScript b...
by strogonoff on Thursday February 13, 2020 @03:08PM
(#22320992)
Back then I recall HTML modules being used as a synonym with HTML imports… It was contrasted with JS modules. Interesting.
Anyway, the standard is there and apparently being worked on so I fail to see how it entirely isn’t a thing—hopefully another incarnation will land.
All around it just feels like a solid way to bundle all the aspects of an element together.