Packages by vmarchaud <contact@vmarchaud.fr> [SYNC profile]

Name IM Last modified Is admin Publish scopes
@vmarchaud Thu Aug 18 2016 19:11:04 GMT+0800 (China Standard Time) false

  • km-trace (latest: 0.0.1) tracing agent of keymetrics
  • pm2-jenkinshook (latest: 1.0.1) receive http hook from jenkins and ask pm2 to reload the application for you
  • deployerjs (latest: 0.2.2) Yet Another Deployement Tool : **soon™**
  • pm2-redis (latest: 2.1.0) PM2 Module to monitor redis
  • pm1 (latest: 0.0.0)
  • km-express-load (latest: 1.2.0) Autoload modules into an Express application instance, config, models, routes, controllers etc...
  • keymetrics-cli (latest: 0.0.3) Command line interface for Keymetrics.io
  • @keymetrics/docker-hub-api (latest: 0.5.3) Docker Hub API is an API library written for NodeJS to access the official Docker Hub/Registry
  • deep-metrics (latest: 0.0.2) ```javascript var monitoring = require('../..').start() monitoring.ee.on('socketio', function(data) { console.log(data) }) ```
  • kmjs-core (latest: 0.5.9) Official Keymetrics API Client for Javascript
  • @keymetrics/pmx (latest: 2.0.0-alpha14) <div align="center"> <a href="http://pm2.keymetrics.io"> <img width=411px src="https://raw.githubusercontent.com/keymetrics/pmx/master/pres/logo.png"> </a> <br/> <b><a href="https://github.com/Unitech/pm2">PM2</a> programmatic integration</b>
  • pm2.io (latest: 2.0.0-alpha16) <div align="center"> <a href="http://pm2.keymetrics.io"> <img width=411px src="https://raw.githubusercontent.com/keymetrics/pmx/master/pres/logo.png"> </a> <br/> <b><a href="https://github.com/Unitech/pm2">PM2</a> programmatic integration</b>
  • @keymetrics/cli (latest: 0.2.0) Command line interface for https://pm2.io/plus
  • pmx (latest: 1.6.7) PM2/Keymetrics advanced API
  • @rlvt/crypt (latest: 1.0.0) Crypt functions (encrypt/decrypt)
  • servicectl (latest: 0.1.1) Servicectl is a opinionated process manager that aim to simplify native init systems for developers.
  • pm2-logrotate (latest: 2.7.0) Module to rotate logs of every pm2 application
  • pm2-githook (latest: 1.10.1) receive http hook from multiple source and ask pm2 to reload the application for you
  • jsdoc-http-plugin (latest: 0.3.2) Plugin to add HTTP Route tags for documenting HTTP endpoints
  • @openprofiling/inspector-heapsnapshot (latest: 0.2.0) This profiler is not advised to run in production (see drawbacks) but can help a lot debuging memory leak in production. It allows taking a snapshot of all the memory current allocated in your application. You will be able to see which type of object are
  • @rlvt/io-ts (latest: 2.1.1) TypeScript compatible runtime type system for IO validation
  • vizion (latest: 2.2.0) Git/Subversion/Mercurial repository metadata parser
  • pm2-deploy (latest: 1.0.2) Deployment system for PM2
  • @openprofiling/inspector-trace-events (latest: 0.2.2) This one isn't really a profier, more like a collector. As defined in the [official documentation](https://nodejs.org/dist/latest-v10.x/docs/api/tracing.html): > Trace Event provides a mechanism to centralize tracing information generated by V8, Node.js c
  • @openprofiling/exporter-file (latest: 0.2.2) This exporter is the simplest one, it will just write the profile to the disk, you can configure the path if needed. The file name will follow the following format:
  • @openprofiling/exporter-s3 (latest: 0.2.2) This exporter is advised when profiling distributed applications where retrieving from each container file system can be hard. It will just write the profile to a remote S3-compatible server, the file name in each bucket will follow the following format:
  • @openprofiling/exporter-gcs (latest: 0.2.2) This exporter is advised when profiling distributed applications where retrieving from each container file system can be hard. It will just write the profile to a remote S3-compatible server, the file name in each bucket will follow the following format:
  • @openprofiling/inspector-cpu-profiler (latest: 0.2.2) This profiler is the recomended one to profile the CPU usage of your NodeJS application. It has a almost-zero impact on performance and specially suited for long-lived application.
  • @openprofiling/inspector-heap-profiler (latest: 0.2.2) This profiler is the recomended one to profile the memory usage per function of your NodeJS application. It has a almost-zero impact on performance and specially suited for long-lived application.
  • @openprofiling/trigger-signal (latest: 0.2.2) This trigger is most probably the easier to use because you just need to send a signal to the process (which is generally straightforward even with containers).
  • @rlvt/tsoa (latest: 3.0.7) Build swagger-compliant REST APIs using TypeScript and Node

Copyright 2014 - 2016 © taobao.org |