dcp-client 4.4.10-0 → 4.4.11-0
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +0 -2
- package/dist/dcp-client-bundle.js +1 -1
- package/dist/dcp-client-bundle.js.map +1 -1
- package/libexec/sandbox/access-lists.js +251 -227
- package/libexec/sandbox/bootstrap.js +16 -2
- package/libexec/sandbox/bravojs-env.js +4 -5
- package/libexec/sandbox/calculate-capabilities.js +3 -1
- package/libexec/sandbox/lift-webgpu.js +232 -197
- package/libexec/sandbox/native-event-loop.js +3 -3
- package/libexec/sandbox/sa-ww-simulation.js +6 -0
- package/package.json +3 -3
package/README.md
CHANGED
|
@@ -243,8 +243,6 @@ very familiar the inner workings of the JavaScript event loop.
|
|
|
243
243
|
## Debugging
|
|
244
244
|
The DCP Compute API includes a function called `localExec` which can be used in place of the `exec` method on the JobHandle. When this function is invoked, a DCP client will create a worker which receives your job from the scheduler, and this job will be limited to that worker. In the browser, this is implemented inside a Web Worker; in NodeJS this is implemented with a standalone worker running within the client process. In either case, it should be possible to use the `debugger` keyword in your work function to trigger a breakpoint in your favourite debugger.
|
|
245
245
|
|
|
246
|
-
*Note:* using localExec on Node.js requires that you install `dcp-client`'s peer dependency, `dcp-worker`.
|
|
247
|
-
|
|
248
246
|
### niim
|
|
249
247
|
The [`niim`](https://www.npmjs.com/package/niim) debugger is a command-line debugger for Node.js which is a fork of node-inspect. If you are debugging a dcp-client with niim and it asks you for a passphrase, use the send function:
|
|
250
248
|
```send "passpharse\n"```
|