
Security News
Deno 2.2 Improves Dependency Management and Expands Node.js Compatibility
Deno 2.2 enhances Node.js compatibility, improves dependency management, adds OpenTelemetry support, and expands linting and task automation for developers.
nanomessage-rpc
Advanced tools
Tiny :hatched_chick: RPC on top of nanomessage
$ npm install nanomessage-rpc
const nanomessagerpc = require('nanomessage-rpc')
;(async () => {
const rpc = nanomessagerpc({
send(buf) {
// implement how to send the message
},
subscribe(next) {
// subscribe for incoming messages
}
})
await rpc
.action('sum', ({ a, b }) => a + b)
.action('subtract', ({ a, b }) => a - b)
.open()
// from the other rpc socket side
const result = await rpc.call('sum', { a: 2, b: 2 }) // 4
})()
We provide a socket helper:
const nanomessagerpc = require('nanomessage-rpc')
const { useSocket } = nanomessagerpc
;(async () => {
const rpc = nanomessagerpc({ ...useSocket(socket) })
// ...
})()
Also it has an emittery instance to emit events through the socket.
;(async () => {
const rpc = nanomessagerpc(socket, opts)
await rpc.open()
rpc.on('ping', () => {
console.log('ping')
})
// from the other rpc socket side
const result = await rpc.emit('ping') // 4
})()
And it has support for nanoerror.
const nanomessagerpc = require('nanomessage-rpc')
const nanoerror = require('nanoerror')
const BAD_REQUEST = nanoerror('BAD_REQUEST', 'the request %s is wrong')
;(async () => {
const rpc = nanomessagerpc(socket, opts)
await rpc
.action('badrequest', () => {
throw new BAD_REQUEST(1)
})
.open()
// from the other rpc socket side
try {
const result = await rpc.call('badrequest', { a: 2, b: 2 }) // 4
} catch (err) {
// will throw BAD_REQUEST: the request 1 is wrong
}
})()
const rpc = nanomessagerpc(options)
Create a new nanomessage-rpc.
Options include:
send: (buf: Buffer) => (Promise|undefined)
: Define a hook to specify how to send the data. Required
.subscribe: (next: function) => UnsubscribeFunction
: Define a handler to listen for incoming messages. Required
.timeout: Infinity
: Time to wait for the response of a request.concurrency: { incoming: 256, outgoing: 256 }
: Defines how many requests do you want to run in concurrent.valueEncoding: buffer-json
: Defines an abstract-encoding to encode/decode messages in nanomessage.rpc.open() => Promise
Opens nanomessage and start listening for incoming data.
rpc.close() => Promise
Closes nanomessage and unsubscribe from incoming data.
rpc.action(actionName, handler)
Defines a rpc action and handler for incoming requests.
actionName: string
: Name of the action.handler: function
: Handler, could be async
.rpc.actions(actions)
Shortcut to define multiple actions.
actions: { actionName: handler, ... }
: List of actions.rpc.call(actionName, data) => Promise<Response>
Call an action an wait for the response.
actionName: string
: Action name.data: (Buffer|Object|String)
: Request data.rpc.emit(eventName, data) => Promise
Call an action an wait for the response.
actionName: string
: Event name.data: (Buffer|Object|String)
: Event data.rpc.on(eventName, handler) => unsubscribe
Subscribe to a RPC event.
Returns an unsubscribe method.
rpc.once(eventName) => Promise
Subscribe to a RPC event only once. It will be unsubscribed after the first event.
Returns a promise for the event data when eventName is emitted.
rpc.off(eventName)
Remove a RPC event subscription.
rpc.events(eventName)
Get an async iterator which buffers data each time a RPC event is emitted.
Call return()
on the iterator to remove the subscription.
for await (const data of rpc.events('ping')) {
console.log(data)
if (disconnected) break
}
You can listen for internal events using rpc.ee
.
on('error', (err) => {})
: When the internal RPC gets an error.on('opened', () => {})
: When the RPC was opened.on('closed', () => {})
: When the RPC was closed.on('request-created', (request, message) => {})
: When a request is created.on('message', (message) => {})
: When it comes a new message.:bug: If you found an issue we encourage you to report it on github. Please specify your OS and the actions to reproduce it.
:busts_in_silhouette: Ideas and contributions to the project are welcome. You must follow this guideline.
MIT © A GEUT project
FAQs
Tiny rpc on top of nanomessage
The npm package nanomessage-rpc receives a total of 161 weekly downloads. As such, nanomessage-rpc popularity was classified as not popular.
We found that nanomessage-rpc 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
Deno 2.2 enhances Node.js compatibility, improves dependency management, adds OpenTelemetry support, and expands linting and task automation for developers.
Security News
React's CRA deprecation announcement sparked community criticism over framework recommendations, leading to quick updates acknowledging build tools like Vite as valid alternatives.
Security News
Ransomware payment rates hit an all-time low in 2024 as law enforcement crackdowns, stronger defenses, and shifting policies make attacks riskier and less profitable.