moleculer-connect
Advanced tools
A command-line interface for connecting to Moleculer microservices
npm install moleculer-connect moleculer-repl@0.6.6
For example, run below command to connect to a Moleculer TypeScript project:
NODE_OPTIONS='--import tsx' moleculer-connect --env --config moleculer.config.ts
The CLI supports several options to customize the connection:
Options:
--version Show version number [boolean]
--help Show help [boolean]
-c, --config Load configuration from a file [string] [default: ""]
--ns Namespace [string] [default: ""]
--level Logging level [string] [default: "info"]
--id NodeID [string] [default: null]
-h, --hot Enable hot-reload [boolean] [default: false]
--serializer Serializer [string] [default: null]
--commands Custom REPL command file mask (e.g.: ./commands/*.js)
[string] [default: null]
👤 Dung Huynh Duc dung@productsway.com
Give a ⭐️ if this project helped you!
Copyright © 2023 Dung Huynh Duc dung@productsway.com.
This project is MIT licensed.
FAQs
Moleculer connect from CLI
The npm package moleculer-connect receives a total of 540 weekly downloads. As such, moleculer-connect popularity was classified as not popular.
We found that moleculer-connect demonstrated a healthy version release cadence and project activity because the last version was released less than 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
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.
Security News
require(esm) backported to Node.js 20, easing the transition to ESM-only packages and reducing complexity for developers as Node 18 nears end-of-life.
