fix: broken package.json commands, broken named imports due to node -…

…-experimental-modules (#153)

* fix(rpc): use export * instead of named import + export because of node --experimental-modules bug

* fix: broken package.json commands

package.json

@@ -17,11 +17,11 @@
   },
   "type": "module",
   "scripts": {
-    "bench": "tsx src/bench.ts",
+    "bench": "tsx src/test/perf/bench.ts",
     "build": "yarn clean && tsc --project ./tsconfig.json",
     "clean": "rm -rf ./build",
     "check:types": "tsc --noEmit",
-    "dev": "tsx watch src/server.ts",
+    "dev": "tsx watch src/cli.ts",
     "prepare": "husky install",
     "lint": "eslint  src/ --color --ext .ts",
     "lint:fix": "yarn run lint -- --fix",

src/network/rpc/index.ts

@@ -2,6 +2,10 @@
 
 import { RPCClient } from './client';
 import { RPCServer } from './server';
-import { RPCHandler } from './interfaces';
 
-export { RPCClient, RPCServer, RPCHandler };
+// node --experimental-modules does not play nicely with exports and refuses to import a default interface even when
+// implementing the fix described here: https://github.com/ardatan/graphql-tools/issues/913
+// Requires further investigating, but export * seems like a decent workaround for now
+export * from './interfaces';
+
+export { RPCClient, RPCServer };