notes | Svelte | |
---|---|---|
9 | 634 | |
583 | 76,553 | |
1.0% | 0.7% | |
7.8 | 9.9 | |
22 days ago | 5 days ago | |
JavaScript | 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.
notes
-
Union, intersection, difference, and more are coming to JavaScript Sets
Has anything changed recently? The proposal has been in stage 3 since November 2022 [1]
[1] https://github.com/tc39/notes/blob/HEAD/meetings/2022-11/nov...
-
The TC-39 just introduced a new stage: stage 2.7
If you're curious about the naming scheme (it now goes 0 -> 1 -> 2 -> 2.7 -> 3 -> 4), then you can read the discussion surrounding the name from the last meeting notes [1].
Also, for a quicker digest, Rob Palmer (from the committee) tweeted about it [2]
[1] https://github.com/tc39/notes/blob/main/meetings/2023-11/nov...
-
JavaScript Type Annotations Proposal Update
Dialog for this update is at https://github.com/tc39/notes/blob/main/meetings/2023-03/mar...
What I would like is a "use: 'typechecked'" at the top of the file indicating that the code has already been checked. This would be accompanied by a new proprosal that defines a standard for what is considered checked (for example checking nullablity in the types) and would allow for browsers to make some optimizations. This could also perhaps reduce the amount of necessary runtime checks such that it would be possible to make it a fully sound typesystem with most of the checks done beforehand.
-
ES Modules Are Terrible
All the meeting notes are recorded here: https://github.com/tc39/notes/tree/main/meetings. You’ll have to do a bit of spelunking in the corresponding agendas and proposal repo to narrow down the exact meetings you’re interested in.
- Proposal withdrawn for JavaScript Function.pipe / flow
- Proposal withdrawn for Function.pipe / flow
-
Deno joins TC39
Here's a list of delegates for TC39, but it doesn't list people by their ECMA member organization.
-
Class fields and private class members are now stage 4, ready for ES2022
This is a good question. I'm not sure I saw the notes of the meeting when this happened, but all the notes are public here: https://github.com/tc39/notes/tree/master/meetings
-
History of JavaScript - How it came into the existence
TC-39 is a group of people who are responsible for the standards. They have meetings every two months with member-appointed delegates and invited experts. You can check the minutes of those meetings here GitHub repository
Svelte
-
My opinion about opinionated Prettier: 👎
the technical decision how Svelte should treat self-closing html elements was hindered by Prettier:
-
Composable architecture example: Go headless (best practices)
Svelte
-
How to optimise React Apps?
React has introduced measures like batching state updates, background concurrent rendering and memoization to tackle this. My opinion is that the best way to solve the problem is by improving their reactivity model. The app needs to be able to track the code that should be re-run on updating a given state variable and specifically update the UI corresponding to this update. Tools like solid.js and svelte work in this manner. It also eliminates the need for a virtual DOM and diffing.
-
Episode 24/13: Native Signals, Details on Angular/Wiz, Alan Agius on the Angular CLI
Similarly to Promises/A+, this effort focuses on aligning the JavaScript ecosystem. If this alignment is successful, then a standard could emerge, based on that experience. Several framework authors are collaborating here on a common model which could back their reactivity core. The current draft is based on design input from the authors/maintainers of Angular, Bubble, Ember, FAST, MobX, Preact, Qwik, RxJS, Solid, Starbeam, Svelte, Vue, Wiz, and more…
- Rich Harris: Svelte parses HTML all wrong
- Mario meets Pareto: multi-objective optimization of Mario Kart builds
- Svelte parses HTML all wrong
-
Svelte for Beginners: Easy Guide
Svelte is a powerful web framework that offers a fresh approach to building web applications. Its simplicity, reactivity model, and built-in features make it an excellent choice for developers looking to create efficient and maintainable applications. By following this guide, you should now have a good understanding of how to get started with Svelte and build your first components, routes, and transitions. You can read more about svelte on the official Svelte website.
-
Trying to use dotnet watch with Svelte
Use .NET features (especially dotnet watch) as a setup for a client-side Svelte application, starting from a simple C# console app.
What are some alternatives?
proposal-class-fields - Orthogonally-informed combination of public and private fields proposals
Alpine.js - A rugged, minimal framework for composing JavaScript behavior in your markup.
proposals - Tracking ECMAScript Proposals
lit - Lit is a simple library for building fast, lightweight web components.
proposal-pipeline-operator - A proposal for adding a useful pipe operator to JavaScript.
solid - A declarative, efficient, and flexible JavaScript library for building user interfaces. [Moved to: https://github.com/solidui/solid]
proposal-function-pipe-flow - A proposal to standardize helper functions for serial function application and function composition.
qwik - Instant-loading web apps, without effort
esm.sh - A fast, smart, & global CDN for modern(es2015+) web development.
awesome-blazor - Resources for Blazor, a .NET web framework using C#/Razor and HTML that runs in the browser with WebAssembly.
proposal-decorators - Decorators for ES6 classes
Next.js - The React Framework