observable
proposal-signals
observable | proposal-signals | |
---|---|---|
9 | 5 | |
516 | 2,379 | |
1.4% | - | |
8.2 | 8.5 | |
about 13 hours ago | 21 days ago | |
Bikeshed | TypeScript | |
GNU General Public License v3.0 or later | 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.
observable
- Proposal: Signals as a Built-In Primitive of JavaScript
-
What We Need Instead of "Web Components"
> especially since Observables have been widely available and actively worked on for a long time, without seeing wide adoption
Take a look at "Userland libraries" section [0] of the proposal (almost certainly written by Ben). He argues that observables get reinvented in the userland in various libraries over and over again. It is a primitive, like a Promise, only better.
[0] - https://github.com/WICG/observable?tab=readme-ov-file#userla...
- Observable API Proposal
- Observable API proposal
-
You Don't Need to “Learn” Svelte: Embracing the Simplicity of JavaScript
Perhaps this falls into the repetitive boilerplate category you referred to, but if you want framework-agnostic domain objects that still work well with Svelte, create your own using the observer pattern.
Create an object with a subscribe method and whatever other methods make sense for updating its state. Svelte will treat it like one of its stores, and it will work with the $ syntax. It can be used with React via its `useSyncExternalStore` hook. It can be used with SolidJS via its `from` utility.
If you don't want to handle the set-up boilerplate, you could use another library like Effector or RxJS, but of course, that means another dependency. There is a gradual move to make something like this a part of the platform[1], but who knows when or if it will land.
[1] https://github.com/domfarolino/observable
proposal-signals
-
This Month in Solid #2: Welcome to ClownTown, Start docs, and more 😎
🤩 JavaScript TC39 Signals standard proposal
-
🤯 Keep Up With these 50 Articles
A proposal to add signals to JavaScript (https://github.com/proposal-signals/proposal-signals) by Rob Eisenberg and Daniel Ehrenberg Personally, I like the addition, but I'd prefer some refinement on the proposal first.
-
HTML Streaming Over the Wire 🥳: A Deep Dive
Regarding the first point, Brisa obviates the need to pass data for stateful components, as client components utilize real DOM elements, namely web components. When attributes are modified, they react to changes using signals, updating their content while preserving the state. Hence, use native constructs—web components, signals (currently as a proposal in TC39 with stage 0), and HyperText Markup Language—made more sense.
-
Episode 24/13: Native Signals, Details on Angular/Wiz, Alan Agius on the Angular CLI
View on GitHub
- Proposal: Signals as a Built-In Primitive of JavaScript
What are some alternatives?
starfx - A modern approach to side-effect and state management for web apps.
proposal-async-iterator-helpers - Methods for working with async iterators in ECMAScript
proposal-observable - Observables for ECMAScript
BrightFutures - Write great asynchronous code in Swift using futures and promises
Reactor - Powering your RAC architecture
bruh - The thinnest possible layer between development and production for the modern web.