material-web
proposal-decorators
Our great sponsors
material-web | proposal-decorators | |
---|---|---|
10 | 64 | |
8,604 | 2,646 | |
4.1% | 1.2% | |
9.8 | 4.2 | |
3 days ago | about 2 months ago | |
TypeScript | ||
Apache License 2.0 | - |
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.
material-web
- Web Components e a minha opinião sobre o futuro das libs front-end
-
Making Web Component properties behave closer to the platform
For example, all the following design systems can be used without tooling (some of them provide ready-to-use bundles, others can be used through import maps): Google's Material Web, Microsoft's Fluent UI, IBM's Carbon, Adobe's Spectrum, Nordhealth's Nord, Shoelace, etc.
-
Google Material Web
Guess there was a 1.0 3 weeks ago: https://github.com/material-components/material-web/discussi...
-
I shaved 80 MB from my TypeScript build by removing googleapis
There is a new “official” one in the works here [1] that uses lots of the “latest and greatest stuff” and should be very fast when it’s finished (later this year). As far as I know it’s set to become the new default company wide implementation of Material on web.
[1] https://github.com/material-components/material-web
-
Using native form with web components + felte no data being passed
I'm using material-web web components inside a form with felte.dev
- Easiest Front-End framework for backend developers?
-
Phoenix with Material Design
If you're going for full SSR and don't want to have to worry about JavaScript, I'd just grab the MDC web components library from Google. That's going to be the easiest time you'll have without implementing a front end framework.
-
Announcing Silkenweb: A reactive VDOM-less web framework using plain rust syntax
Ultimately, I'd like to be able to write reasonably complex client/server web apps in Rust, so the next medium term thing on my list is web components (as a consumer). That'll allow a lot of existing Javascript components to be reused. For example: Microsoft Fast, Material Web Components and UI5.
-
List of Web Component libraries and systems
Material Design (Google)
- Material design on typescript without angular
proposal-decorators
-
Making Web Component properties behave closer to the platform
Because many rules are common to many attributes (the coerceType operation is defined by WebIDL, or using similar rules, and the HTML specification defines a handful of microsyntaxes for the parseValue and stringifyValue operations), those could be packaged up in a helper library. And with decorators coming to ECMAScript (and already available in TypeScript), those could be greatly simplified:
-
The case for using decorators in your codebase
Decorators are currently not a part of the standard JavaScript language. They are still being discussed in tc39 and have reached proposal stage 3. This means the spec has more or less stabilized and we can use them but they would be transplied before being run in the browser. This would be done via babel or tsc for most users
-
JavaScript Naming Conventions are Important
JavaScript was created a long time ago, and at the time of its inception, the authors decided not to use affirmative prefixes for boolean names. Now, they do their best by continuing to follow their convention, even if it goes against the community's opinion. Even if the authors wanted to introduce new naming conventions in the specification, they could not do it, at least not coherently. Old code cannot be renamed because JavaScript must remain backward-compatible. And starting to write new code using new approaches is not a great idea either, as there would be two ways to do the same thing, which is also undesirable.
-
ECMAScript Decorators. The Ones That are Real
2016-07 – Stage 2. After the decorators proposal reached stage 2, its API began to undergo significant changes. Furthermore, at one point the proposal was referred to as "ESnext class features for JavaScript." During its development, there were numerous ideas about how decorators could be structured. To get a comprehensive view of the entire history of changes, I recommend reviewing the commits in the proposal's repository. Here is an example of what the decorators API used to look like:
-
Strawberry - Zero-Dependency, Build-Free JavaScript Framework
The example you've given isn't valid JavaScript, JS doesn't have decorators. (Although there is a stage 3 tc39 for it, afaik no browser has implemented it)
-
Updates from the 96th TC39 meeting
There was a decorators issue brought up in the meeting (issue 508) and decorators metadata, as noted in the article, is now at stage 3. So there's still active work being done on decorators. If I had to guess, I'd say they'd be a likely candidate for ES2024.
-
The Lightweight Alternative to GraphQL, Resolvers Instead of Endpoints
As per the proposal, decorators can be used with Classes and their elements such as fields, methods, and accessors. To leverage this feature, we need to ensure that our resolvers provider is an instance of a Class. Therefore, we will modify the code in src/api/users/users-resolvers.js to the following:
-
Using modern decorators in TypeScript
The modern version of decorators, which will be officially rolled out in TypeScript 5.0, no longer requires a compiler flag and follows the official ECMAScript Stage-3 proposal. Alongside a stable implementation that follows ECMAScript standards, decorators now work seamlessly with the TypeScript type system, enabling more enhanced functionality than the original version.
-
What should I do after react js
100% this. Going in depth of libraries will make you so much better developer than learning newest and coolest frameworks in JS ecosystem. Learn to create your own React, Promises, or anything you like in JS. It will give you immense perspective about these libraries. Once you start understanding them you will feel like they are not that complex and you can do it too. Go read TC39 proposals and issues people point out in them. You will see how JS is borrowing features from other languages.
-
Announcing TypeScript 5.0
The actual proposal gives the "@reactive" decorator as the first example, which just so happens is the only decorator that I use in my library with TypeScript's legacy decorator option. Was so happy to see they recognize this use case! https://github.com/tc39/proposal-decorators
What are some alternatives?
sycamore - A library for creating reactive web apps in Rust and WebAssembly
openapi-typescript - Generate TypeScript types from OpenAPI 3 specs
lwc - ⚡️ LWC - A Blazing Fast, Enterprise-Grade Web Components Foundation
proposals - Tracking ECMAScript Proposals
patternfly-elements - PatternFly Elements. A set of community-created web components based on PatternFly design.
remult - Full-stack CRUD, simplified, with SSOT TypeScript entities
solid - A declarative, efficient, and flexible JavaScript library for building user interfaces.
TypeORM - ORM for TypeScript and JavaScript. Supports MySQL, PostgreSQL, MariaDB, SQLite, MS SQL Server, Oracle, SAP Hana, WebSQL databases. Works in NodeJS, Browser, Ionic, Cordova and Electron platforms.
spectrum-web-components - Spectrum Web Components
proposal-decorator-metadata
silkenweb - A library for writing reactive single page web apps
arktype - TypeScript's 1:1 validator, optimized from editor to runtime