community-protocols
React
community-protocols | React | |
---|---|---|
8 | 1,702 | |
168 | 222,406 | |
0.0% | 0.8% | |
5.4 | 9.9 | |
about 1 month ago | 4 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.
React
-
Weather Application using ReactJS | react mini project
ReactJS React js. CSS. JSX. Function Components in React.
- Backend-Genese: Von PHP zu Node.js & TypeScript (Teil 1)
-
Mastering Code Quality: Setting Up ESLint with Standard JS in TypeScript Projects
JavaScript Standard Style is less opinionated about JSX formatting and largely leaves JSX as-is. In a React project, you should integrate with React-specific linting rules for ESLint. The generally accepted configurations are eslint-plugin-react and eslint-plugin-react-hooks, enforcing some best practices of writing React code.
-
Inflight Magazine no. 9
We are continuing to add new project templates for various types of projects, and we've recently created one for the infamous combination of React with Vite tooling.
-
"Kawaii" tech logos by Sawaratsuki
Go to https://react.dev/?uwu=true for a surprise.
-
Building an Email Assistant Application with Burr
You can use any frontend framework you want — react-based tooling, however, has a natural advantage as it models everything as a function of state, which can map 1:1 with the concept in Burr. In the demo app we use react, react-query, and tailwind, but we’ll be skipping over this largely (it is not central to the purpose of the post).
-
React 18.3.0 Is Out
Oddly, no info on changelog: https://github.com/facebook/react/blob/main/CHANGELOG.md
-
Preact vs React: A Comparative Guide
In this post, we get to know more about Preact, one of this year's trending libraries. And we'll compare it to React to see which one suits better for our projects.
-
Meet Cheryl Murphy: Full-Stack Developer, lifelong learner, and volunteer Project Team Lead at Web Dev Path
Cheryl Murphy is not only a dedicated full-stack web developer skilled in technologies like React, Next.js, and NestJs but also a community-driven professional who recently took on the role of volunteer project team lead at Web Dev Path. With a dual Bachelor's degree in Computing and Chemical Engineering from Monash University, Cheryl’s journey in tech is marked by a passion for building accessible solutions and a commitment to fostering community within tech.
-
How to Build an AI FAQ System with Strapi, LangChain & OpenAI
Basic knowledge of ReactJs
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
qwik - Instant-loading web apps, without effort
vscode-webview-ui-toolkit - A component library for building webview-based extensions in Visual Studio Code.
Alpine.js - A rugged, minimal framework for composing JavaScript behavior in your markup.
soci-frontend - [Moved to: https://github.com/jjcm/nonio-frontend]
Vue.js - This is the repo for Vue 2. For Vue 3, go to https://github.com/vuejs/core
services-as-dom-elements
SvelteKit - web development, streamlined
nx-console - Nx Console is the user interface for Nx & Lerna.
lit-element - LEGACY REPO. This repository is for maintenance of the legacy LitElement library. The LitElement base class is now part of the Lit library, which is developed in the lit monorepo.
ficusjs - FicusJS is a set of lightweight functions for developing applications using web components
Tailwind CSS - A utility-first CSS framework for rapid UI development.