as @jvilk pointed out in #1, jvilk/BrowserFS provides ApiErrors to callbacks, which have a pretty toString method. We lose this when we send these errors from the kernel to the worker (due to structured cloning "The prototype chain does not get walked and duplicated").
We should provide full ApiErrors to users of the fs module in browser-node. BrowserFS's WorkerFS does this - we should probably just use that same mechanism
bpowers
commented
8 years ago
as @jvilk pointed out in #1, jvilk/BrowserFS provides
ApiErrors to callbacks, which have a prettytoStringmethod. We lose this when we send these errors from the kernel to the worker (due to structured cloning "The prototype chain does not get walked and duplicated").We should provide full
ApiErrors to users of thefsmodule inbrowser-node. BrowserFS's WorkerFS does this - we should probably just use that same mechanism