proposal-decorator-metadata VS proposal-function-once

Indeed, numerous proposals and extensions are being considered to enhance the decorators specification further. Some of these proposals like the Decorator Metadata, are already under consideration even though the core decorator specification has not yet been standardized. This underscores the idea that decorators have a promising future in the specification and we can hope to see them become a part of the standard in the near future.

Decorator Metadata: Extend the Decorators proposal by adding the ability for decorators to associate metadata with the value being decorated.

https://github.com/tc39/proposal-decorator-metadata is where we'd probably need to begin to store this information. It's still need a transpiler to generate the necessary decorators. Decorators are still in progress (but kind of seemingly shaping up these days).

Decorator metadata: Decorators can associate metadata with the value that is being decorated. (P.S: The repo shall be updated with content.)

There are possible solutions: - top-level await - const GRIDS1 = await foo() - dispatching a custom event when setting and listening in the components - wrapping everything in an async function - state management - memoizing the function and await it in the components (see https://github.com/tc39/proposal-function-once for a stage 1 proposal of func.once()

Function once: Standardize once function in the language core.