proposal-decorators

Decorators for ES6 classes (by tc39)

Proposal-decorators Alternatives

Similar projects and alternatives to proposal-decorators

NOTE: The number of mentions on this list indicates mentions on common posts plus user suggested alternatives. Hence, a higher number means a better proposal-decorators alternative or higher similarity.

proposal-decorators reviews and mentions

Posts with mentions or reviews of proposal-decorators. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2024-01-21.
  • Making Web Component properties behave closer to the platform
    9 projects | dev.to | 21 Jan 2024
    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
    1 project | dev.to | 10 Jan 2024
    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
    5 projects | dev.to | 14 Nov 2023
    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
    6 projects | dev.to | 24 Oct 2023
    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
    2 projects | /r/javascript | 2 Jun 2023
    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
    5 projects | /r/javascript | 19 May 2023
    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
    2 projects | dev.to | 2 May 2023
    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
    4 projects | dev.to | 2 May 2023
    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
    2 projects | /r/developersIndia | 28 Apr 2023
    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
    1 project | /r/javascript | 16 Mar 2023
    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
  • A note from our sponsor - WorkOS
    workos.com | 25 Apr 2024
    The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning. Learn more →