-
Notifications
You must be signed in to change notification settings - Fork 3
feat: add remote env to node env manager #2732
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
move createFeatureEnvironmentsMapping to cli (where it's used) move files and imports accordingly
barak007
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
looking good. hard to know if the socket connect is good without running the app. I assume you run dev and it's fine.
|
we should go with major. let me know if you want me to release it |
| env.endpointType === 'single' ? env.env : `${envName}/${this.envInstanceIdCounter.next(envName)}`; | ||
| const worker = runWorker(envInstanceId, this.createEnvironmentFileUrl(envName), runtimeOptions); | ||
| const runningEnv = await connectWorkerToProxyCom(envName, worker, forwardingCom); | ||
| let runningEnv; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
type
| }); | ||
| }); | ||
|
|
||
| function getClientComm(port: number) { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
com*
devServerPorttoenginePort