@gloch96/typed-getters

Project name: typed-getters (2024 edition)

IDEA! : Using JSDocs in tandem with typed-getters could become a lightweight alternative over TypeScript .

MOTIVATION

Unlike default EcmaScript (JavaScript) constructors such as String() defaults to '' | Number() defaults to 0 | Symbol() defaults to Symbol() | Boolean() defaults to false whereas each by specification defaults to some value, the typed-getters helps to maintain consistency among JavaScript primitive simply returning a graceful undefined

HOW TO USE

Installation

Run the command npm i -g @gloch96/typed-getters : this will install the util at $ echo "$(npm root -g)" . When you import this util (package), use following ESM signature :

import { new$ } from 'typed-getters/src/index.mjs';

Please refer to ./src/tests/ running each test as node /src/tests/test_name.mjs | whereas "test_name" := instance | factor (you get the idea) ; each test example is ESM-friendly script that can be evaluated in both run-times : browser of choice and Node.js .

Source

Consider the following code excerpt of our node /src/tests/instance.mjs example as follows :

class Name$sruct {

    constructor(){
        // constructor implements typed-getters via its accessors (refer to ./src/index.mjs for TypedMap)
    }

}

class Name$interface extends Name$sruct {

    methodDeclaration(){
        // decoupled prototype for will-be instance of Name$sruct
    }

}

From the code above, we see that it only makes sense (decoupling) prototype from its related instance if we are duck-typing . Of course, we could achieve similar idea using Reflect.apply (refer to ./src/tests/factor.mjs), however in turn it would return factor rather than instance as our new$ named export essentialy is nothing else than a slighly modified Reflect.construct.

---

Happy coding ♥ projektorius96