Bundeling error exposing /home on server connect code ?

On paste of the code from: https://github.com/socketio/socket.io/blob/master/examples/chat/index.js
My assumption this is because of the code creating a server and listner ports. I wonder if this is at all possible inside a browser without a runtime with specific bindings for JS.

Bundling error:

---FLAGRANT SYSTEM ERROR---

--- error #0: ---

(logs uuid: f7cd2440-535a-11ea-84d6-1530f0a1912b )

Error: "ENOENT: no such file or directory, open '/home/wzrd/package.json'"

cause: { [Error: ENOENT: no such file or directory, open '/home/wzrd/package.json']
errno: -2,
code: 'ENOENT',
syscall: 'open',
path: '/home/wzrd/package.json' }
isOperational: true
errno: -2
code: ENOPACKAGEJSON
syscall: open
path: /home/wzrd/package.

Start by reproducing the bundling request using the Socket.IO chat example linked in the issue and inspect how wzrd.in handles its server-side dependencies and package.json lookup. Determine whether the server-connect code can be bundled for a browser, then document or fix the behavior so the request no longer exposes the /home path and has a clear supported outcome.

Written by the indexing model from the issue text.