Security News
Opengrep Emerges as Open Source Alternative Amid Semgrep Licensing Controversy
Opengrep forks Semgrep to preserve open source SAST in response to controversial licensing changes.
@ch1/rpc-worker
Advanced tools
This is not well maintained
This is not traditional RPC, but it is like it
yarn add @ch1/rpc-worker
Slightly easier API than in the raw @ch1/rpc
Main JS Script
import * as wrpc from '@ch1/rpc-worker';
const w = new Worker(TEST_FILE);
const rpc = wrpc.create({ worker: w });
rpc.ready
.then(() => rpc.remote.foo())
.then(result => {
expect(result).toBe(7);
done();
})
.catch(done);
Worker JS
import * as wrpc from '@ch1/rpc-worker';
wrpc.create(undefined, {
foo: () => new Promise(resolve => resolve(7)),
});
onDestroy
RPC<RemoteType>.destroy()
will call terminate on the workerimport * as wrpc from '@ch1/rpc-worker';
const w = new Worker(TEST_FILE);
const rpc = wrpc.create({ worker: w });
rpc.ready
.then(() => rpc.remote.foo())
.then(result => {
expect(result).toBe(7);
done();
})
.catch(done);
// handle onDestroy here
rpc.onDestroy((reason?: string) => {
// cleanup, restart, whatever
});
The worker extension is pretty much as described above. For more information
on the RPC<RemoteType>
object see the
@ch1/rpc docs
1.1.0
@ch1/rpc
to use version with onDestroy
FAQs
JavaScript Remote Procedure Call (RPC) - Web Worker Adapter
The npm package @ch1/rpc-worker receives a total of 3 weekly downloads. As such, @ch1/rpc-worker popularity was classified as not popular.
We found that @ch1/rpc-worker demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 1 open source maintainer collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
Opengrep forks Semgrep to preserve open source SAST in response to controversial licensing changes.
Security News
Critics call the Node.js EOL CVE a misuse of the system, sparking debate over CVE standards and the growing noise in vulnerability databases.
Security News
cURL and Go security teams are publicly rejecting CVSS as flawed for assessing vulnerabilities and are calling for more accurate, context-aware approaches.