TNG name about tng-hooks

[damassi]

Ok this makes sense! thank you for explaining 👍

[getify]

The TNG (pronounced "ting") name has a few meanings/reasons:

• It started as "totally not globals" -- a nod to the idea that it's like having global storage but not-global because it's in closures

• I planned a talk to introduce TNG, called "State Track: The Next Generation" (a nod to star trek TNG, etc)

• It's hard to get unique names on npm these days, especially in the realm of react/hooks/etc. TNG is a nice unique moniker.

---

My thought was, if people didn't like using the name TNG, they can always call it some other name. In node: var { TNG: coolHooks, .. } = require("tng-hooks");. In the browser, window.coolHooks = window.TNG;.

[getify]

Why not "makeHooks" or import { useState } from 'fn-hooks'? etc. To invoke everything with "TNG" doesn't seem meaningful language-wise.

I don't have TNG exporting itself as an ES6 module yet, but the various hooks, like useState(..), etc, are in fact individual "exports" on the API of this lib. You don't say TNG.useState(..), you just say useState(..) (just like in React).

That's why in node you do var {TNG,useState,useEffect} = require("tng-hooks");, because you're individually "importing" each of those "exported" identifiers as you see fit.

The only time you use the TNG name itself is for the function that creates the wrapped/hooked functions (aka "Articulated Functions"). And as I said above, if you don't like saying myFunc = TNG(myFunc);, you can rename TNG to whatever you prefer, like makeHooks(..) or whatever, and then say myFunc = makeHooks(myFunc);.