A novel approach to reusable web components

1. htmx

   1 653 45,276 9.4 JavaScript

   </> htmx - high power tools for HTML

   

2. Stream

   getstream.io featured

   Stream - Scalable APIs for Chat, Feeds, Moderation, & Video. Stream helps developers build engaging apps that scale to millions with performant and flexible Chat, Feeds, Moderation, and Video APIs and SDKs powered by a global edge network and enterprise-grade infrastructure.

   

3. lit

   2 181 19,910 8.3 TypeScript

   Lit is a simple library for building fast, lightweight web components.

   

   I'm guess that since this is an academic paper and not say, a website or GitHub repo, that you're in school. But given the research paper nature of this, did you want to contrast and compare to other methods of authoring web components?

   There are many existing and popular approaches out there. Is your take easier, faster, or more capable? That discussion would be interesting.

   Two that I help maintain are Lit (https://lit.dev) and Heximal (https://heximal.dev/). Of those, Heximal might share the most with Zjs.

4. ZjsComponent

   3 2 19 4.3 JavaScript

   Companion code for the paper introducing ZjsComponent

   

   Thanks to the availability of ChatGPT and Claude, I have actually checked all those links prior to creating my own.

   The ZjsComponent thing I use is unlike those things; while the goal of those (and other similar projects) is primarily to perform client-side includes, the goal of zjs-component is to provide client-side object instantiation using a remote object definition.

   The paper itself may be a bit arcane and obscure, but as a quick example of what zjs-component was intended to do, see the GH page: https://github.com/lelanthran/ZjsComponent/tree/master?tab=r...

   As you'll see from the above link, the goal was not to simply include remote fragments (with some execution behaviour), but to instantiate a local instance of an object defined in a remote file fragment and support instance-scoped code and HTML.

   IOW, it's the scoping to a specific instance that is different from the existing `include` or `import` libraries.

   It means when you do this (assuming you wrote a counter-obj.zjsc object):

5. Drab

   4 2 883 0.0 Elixir

   Remote controlled frontend framework for Phoenix.

   

6. html-import

   5 1 17 - TypeScript

   Custom element for importing (parts of) HTML documents into other documents

   

7. html-imports

   6 1 74 - HTML

   Discontinued HTML Imports polyfill

   

8. SSDataSources

   7 1 199 - Objective-C

   Flexible data sources for your UITableView and UICollectionView.

   

9. InfluxDB

   www.influxdata.com featured

   InfluxDB – Built for High-Performance Time Series Workloads. InfluxDB 3 OSS is now GA. Transform, enrich, and act on time series data directly in the database. Automate critical tasks and eliminate the need to move data externally. Download now.

   

10. SDWebImage

    8 8 25,376 8.0 Objective-C

    Asynchronous image downloader with cache support as a UIImageView category

    

Suggest a related project