community-protocols
open-wc
community-protocols | open-wc | |
---|---|---|
8 | 18 | |
168 | 2,213 | |
0.0% | 0.9% | |
5.4 | 8.1 | |
about 1 month ago | 19 days ago | |
JavaScript | ||
- | MIT License |
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.
community-protocols
-
What We Need Instead of "Web Components"
> except that "reactivity" does not meet the bar of developers collectively having landed on a solution to a common problem
Now that everyone seems to be in love with signals, there is work going on in the web components community group to prepare a spec for a signal (or observable, not sure what they are trying to call it) primitive [0]. It seems that they are getting ready to bring it to TC39 as a proposal.
(In the meantime, the Observable primitive from rxjs been given a go-ahead for browser implementation. There is a proposal ready [1], and I think I heard that it may already be in Chrome behind a flag [2].
So yeah; it's gonna be fun. Especially if both groups call their primitive Observable :-)
0 - https://github.com/webcomponents-cg/community-protocols/issu...
1 - https://github.com/WICG/observable
2 - https://nitter.net/BenLesh/status/1737174784406933599
-
Show HN: Hyphen β custom element base class for good ergonomics
The custom element spec definitely only deals with the mechanics of when are where to run your component's lifecycle code - it says nothing about data. So your choices are basically property accessors, which are interoperable, but require prop-drilling for global-ish data, or something proprietary like a state management library.
The Web Components Community Group (WCCG) is offering something of a third way with the community protocols: https://github.com/webcomponents-cg/community-protocols
The Context protocol provides tree-scoped ambient data in an interoperable way. It's implemented by Lit and FAST (I believe). It doesn't replace a data store, but it's often used to provide data stores to components, and at least reduce some coupling.
-
Events are the shit
Did you know events can also carry promises? A great showcase of this pattern is the Pending Task Protocol by the Web Components Community Group. Now, "Pending Task Protocol" sounds very fancy, but really, it's just an event that carries a promise.
-
Nx Console gets Lit
If youβre coming from the Angular world, you probably appreciate the great dependency injection (DI) mechanism they have. You can centrally define some services and reuse them across your app, without thinking about passing on props from component to component - the DI system takes care of it. Lit provides something similar via the [@lit-labs/context](https://lit.dev/docs/data/context/) package. Itβs based on the Context Community Protocol and similar to Reactβs context API.
-
Back to the Front-end: Exploring the Future of the Umbraco UI (Part 9 - Context API)
Fundamentally it is an event based mechanism to access state or "context" from ancestores of a component node. Based on the Web Components Context Protocol RFC which in turn is inspired by React's Context Api, the key purpose is to solve the problem of prop drilling.
- π 8 Days of Web Components Tips
-
JavaScript vs JavaScript: Round 2. Fight!
The conversation led to the creation of https://github.com/webcomponents-cg/community-protocols. So there is some effort to standardize at least on convention for these higher-order considerations, but working through this and how opinionated it is made me recognize even more that this has a lot of similarities to a different group building a different framework. Tricky balance.
-
We Use Web Components at GitHub
Iβm pretty actively following a lot of the web components community so I thought I would jump in here with some hopefully helpful information. Depending on what you mean by SEO itβs worth noting that for a while now Google and I believe Bing and a few others havenβt had any kind of requirement to pre-render content. You can just serve standard web components or any kind of SPA style front end and it will get indexed just fine, no penalties and no real issues unless youβre doing something particularly strange.
However, one of the more exciting projects in the web components space (lit.dev) now also supports proper SSR as well which is a very new thing in the world of web components. They are trying to build it in such a way that any other library can take advantage of through a common interface.
In fact there are some kind of early stage talks happening over here https://github.com/webcomponents/community-protocols where a bunch of companies like Google, Adobe, ING and others are trying to develop some open protocols on a whole bunch of topics to improve interoperability between various libraries so that no one has to buy in 100% to any one setup.
open-wc
-
Testing Web Components with @web/test-runner
npm init @open-wc@latest Need to install the following packages: @open-wc/[email protected] Ok to proceed? (y) y _.,,,,,,,,,._ .d'' ``b. Open Web Components Recommendations .p' Open `q. .d' Web Components `b. Start or upgrade your web component project with .d' `b. ease. All our recommendations at your fingertips. :: ................. :: `p. .q' `p. open-wc.org .q' `b. @openWc .d' `q.. ..,' See more details at https://open-wc.org/init/ '',,,,,,,,,,'' Note: you can exit any time with Ctrl+C or Esc β What would you like to do today? βΊ Scaffold a new project β What would you like to scaffold? βΊ Web Component β What would you like to add? βΊ Testing (web-test-runner) β Would you like to use typescript? βΊ Yes β What is the tag name of your web component? β¦ testing-components ./ βββ testing-components/ β βββ .vscode/ β β βββ extensions.json β βββ demo/ β β βββ index.html β βββ src/ β β βββ index.ts β β βββ testing-components.ts β β βββ TestingComponents.ts β βββ test/ β β βββ testing-components.test.ts β βββ .editorconfig β βββ .gitignore β βββ LICENSE β βββ package.json β βββ README.md β βββ tsconfig.json β βββ web-dev-server.config.mjs β βββ web-test-runner.config.mjs β Do you want to write this file structure to disk? βΊ Yes Writing..... done β Do you want to install dependencies? βΊ Yes, with npm
-
Are web components still a thing?
Very much still a thing, https://open-wc.org/ is a good resource for examples and best practices.
-
Alternative to tailwind for Vite + Lit + Ts ?
I have this design system project for a company, I need to make web components and instead of using open-wc.org pre-built, I chose to go Vite.
-
How my Frontend skills helped me pass my sailing test
Nice. We have data with meaning. Now let's create the presentation layer (aka the UI!) and then let's add interactivity to the UI, so we can have feedback when actually simulating an exam (aka the Frontend!). Since in ING we are advocates of Web Components, I always wanted to give this stack a try for side projects. I jumped right into open-wc.org and used the npm generator. Everything worked precisely as expected. It was a breeze since my Chapter is using lit every. single. day. So I could finally get some mileage myself, in writing lit. At work, as a Chapter Lead, I prefer to spend my time more effectively for the team, rather than coding new features by myself; my chapter does it better anyway (#proud).
- Ask HN: What's is your go to toolset for simple front end development?
-
[AskJS] Looking for contributors for open source project / custom web element
I suggest following these best practices for creating a custom web element: https://open-wc.org/
- Open Web Components
- Open Web Components provides guides, tools, and libraries for developing web components
-
Start Using Web Components with open-wc
Open Web Components is a great tool for accessing open-source web components and is very easy to set up with their quickstart guide and easy to understand documentation.
-
Getting Started with Wireframes & Prototypes for Applications
This application is one of many applications out there that are dipping their toes in the land of web components. Web components are still very new and ever-growing. While I have been developing on HAX-the-Web, I am also the Project Manager for HAXCamp 2022. < hax-camp > is an unconference dedicated to all things Web Components!This year's event is being student-run and we anticipate there being discussions about openwc, lit, performance, element composition, css, hax.psu, pedagogy, and design systems. If this work flow is something that you are interested in, I would encourage signing up for this event. It is much more than this, larger than you know and a way to connect with students, faculty, staff, and professional in the industry.
What are some alternatives?
web3-sign-msg - web3-sign-msg is a modern web component built with ficusjs to sign messages with your eth private key in Metamask
turborepo - Incremental bundler and build system optimized for JavaScriptΒ and TypeScript, written in Rust β including Turborepo and Turbopack. [Moved to: https://github.com/vercel/turbo]
vscode-webview-ui-toolkit - A component library for building webview-based extensions in Visual Studio Code.
rocket - The modern web setup for static sites with a sprinkle of JavaScript
soci-frontend - [Moved to: https://github.com/jjcm/nonio-frontend]
React - The library for web and native user interfaces.
web - Guides, tools and libraries for modern web development.
services-as-dom-elements
custom-elements-manifest - A file format for describing custom elements
nx-console - Nx Console is the user interface for Nx & Lerna.
ficusjs - FicusJS is a set of lightweight functions for developing applications using web components