Missing config in $PATH

[eL1x00r]

When using npx / npm i -g or installing the library from npmjs, we got the issue of config module accessing NULL config file leading to an error.

This occurs due to config lib searching for the config file in current PWD path ( which is whatever path the shell is located at with global npmjs bin execution.

Fixes would be :

• utilizing __filename/__dirname or relative path loading on runtime for global,
  AND
• programmatic library usage should offer option to provide peer channel public key as parameter for initReader startup method

❯ npx trac-tap-reader
Need to install the following packages:
[email protected]
Ok to proceed? (y) y
WARNING: No configurations found in configuration directory:/Users/eL1x00r/config
WARNING: To disable this warning set SUPPRESS_NO_CONFIG_WARNING in the environment.
  _____                  ____                 ____                _
 |_   _| __ __ _  ___   / ___|___  _ __ ___  |  _ \ ___  __ _  __| | ___ _ __
   | || '__/ _` |/ __| | |   / _ \| '__/ _ \ | |_) / _ \/ _` |/ _` |/ _ \ '__|
   | || | | (_| | (__  | |__| (_) | | |  __/ |  _ <  __/ (_| | (_| |  __/ |
   |_||_|  \__,_|\___|  \____\___/|_|  \___| |_| \_\___|\__,_|\__,_|\___|_|

Protocol: Ordinals/TAP
/Users/el1x00r/.npm/_npx/d0d1003349eb1dca/node_modules/config/lib/config.js:182
    throw new Error('Configuration property "' + property + '" is not defined');
          ^

[eL1x00r]

new notice:

due to npx and npm i -g might not be running postinstall script for patching corestore bug,
we should avoid exposing a global package.json bin (!) from now.