
Security News
Crates.io Users Targeted by Phishing Emails
The Rust Security Response WG is warning of phishing emails from rustfoundation.dev targeting crates.io users.
nodefony-client
Advanced tools
$ npm install nodefony-client
#or
$ yarn add nodefony-client
console.log(nodefony)
{
version: "6.0.0-beta.4",
environment: "development",
isRegExp: ƒ,
isObject: ƒ,
isFunction: ƒ,
Api: ƒ Api()
Container: ƒ Container(services, parameters)
Error: ƒ nodefonyError(message, code)
Events: ƒ Notification(settings, context)
ExtendedScope: ƒ ExtendedScope(name, parent)
PDU: ƒ PDU(pci, severity, moduleName, msgid, msg, date)
Scope: ƒ Scope(name, parent)
Service: ƒ Service(name, container, notificationsCenter)
Socket: ƒ Socket(url)
Storage: ƒ Storage(name)
Syslog: ƒ Syslog(settings)
URL: {parse: ƒ, resolve: ƒ, resolveObject: ƒ, format: ƒ, Url: ƒ}
WebSocket: ƒ Websocket(url)
browser: {flag: "chrome", name: "Chrome", version: "86.0.4240.80"}
environment: "development"
inspect: ƒ inspect(obj, opts)
isArray: ƒ isArray(ar)
isFunction: ƒ isFunction(arg)
isNullOrUndefined: ƒ isNullOrUndefined(arg)
isObject: ƒ isObject(arg)
isRegExp: ƒ isRegExp(re)
isUndefined: ƒ isUndefined(arg)
medias: Medias {MediaStream: ƒ}
nativeWebSocket: true
protocols: {Bayeux: ƒ}
util: {types: {…}, format: ƒ, deprecate: ƒ, debuglog: ƒ, inspect: ƒ, …}
version: "6.0.0-beta.4"
webAudio: {audioContext: ƒ, Mixer: ƒ, AudioBus: ƒ, Track: ƒ}
}
<script type="text/javascript" src="https://cdn.jsdelivr.net/npm/nodefony-client"></script>
<script type="text/javascript" src="https://cdn.jsdelivr.net/npm/nodefony-client/dist/nodefony.js?medias=true&socket=true"></script>
<script type="text/javascript" src="https://cdn.jsdelivr.net/npm/nodefony-client@6.0.0/dist/nodefony.js?medias=true&socket=true"></script>
<script type="text/javascript" src="https://unpkg.com/nodefony-client"></script>
<script type="text/javascript" src="https://unpkg.com/nodefony-client@6.0.0/dist/nodefony.js?medias=true&socket=true"></script>
<script type="text/javascript" src="https://cdn.jsdelivr.net/npm/nodefony-client@6.0.0/dist/nodefony.js?medias=true&socket=true"></script>
medias
socket
webaudio
sip
debug = sip,socket,webaudio,medias | true | flase
environment = production | development
// import base library
import nodefony from "nodefony-client";
// import chunk medias
import media from "nodefony-client/src/medias/medias";
media(nodefony);
// import chunk webaudio
import webaudio from "nodefony-client/src/webaudio/webaudio";
webaudio(nodefony);
// import chunk socket
import socket from "nodefony-client/src/transports/socket/socket";
socket(nodefony);
const nodefony = require('nodefony-client')
//chunk
const socket = require("nodefony-client/src/transports/socket/socket");
socket.default(nodefony);
const notificationsCenter = new nodefony.Events();
notificationsCenter.on("myEvent", (count, args) => {
console.log(count, args)
});
const obj = {foo:"bar"};
let i = 0;
notificationsCenter.emit("myEvent", i, obj);
notificationsCenter.emit("myEvent", ++i, obj);
// 0 {foo: "bar"}
// 1 {foo: "bar"}
// nodefony.Service => (name, container = null, events = null, settings = {})
class myService extends nodefony.Service {
constructor(){
super("myService");
}
}
const instance = new myService();
console.log(instance)
{
container: Container {scope: {…}, services: C…r.protoService, parameters: C…r.protoParameters, protoService: ƒ, protoParameters: ƒ}
name: "myService"
notificationsCenter: Events {_events: {…}, _eventsCount: 1, _maxListeners: 20}
options: {}
settingsSyslog: {moduleName: "myService", defaultSeverity: "INFO"}
syslog: Syslog {_events: {…}, _eventsCount: 0, _maxListeners: undefined, settings: {…}, ringStack: Array(0), …}
}
const syslog = new nodefony.Syslog();
syslog.init();
syslog.log('info', "INFO");
syslog.log('debug', "DEBUG");
syslog.log('notice', "NOTICE");
syslog.log('warning', "WARNING");
syslog.log('error', "ERROR");
syslog.log('alert', "ALERT");
syslog.log('critic', "CRITIC");
syslog.log('emergency', "EMERGENCY");
FAQs
Client Side Nodefony Framework
We found that nodefony-client 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
The Rust Security Response WG is warning of phishing emails from rustfoundation.dev targeting crates.io users.
Product
Socket now lets you customize pull request alert headers, helping security teams share clear guidance right in PRs to speed reviews and reduce back-and-forth.
Product
Socket's Rust support is moving to Beta: all users can scan Cargo projects and generate SBOMs, including Cargo.toml-only crates, with Rust-aware supply chain checks.