loopbackio / loopbackio/loopback4-extension-grpc

Not starting GRPC server

Open
#34 5 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
TypeScript
Stars
18
Forks
8
PR merge metrics
No merged PRs in 30d

Description

# Description/Steps to reproduce
1. Scaffolded a LB 4 app as "loopback4-example-express-composition"
2. $ npm install --save @loopback/grpc
3. Modified Index.ts file with the code explained in the section "Component Configuration" of https://www.npmjs.com/package/@loopback/grpc
4. Followed the rest of the steps as mentioned in npm module "@loopback/grpc"

# Link to reproduction sandbox

# Expected result
1. Suppose to generate "greeter.proto.ts", but it never generate the .tc file for the proto file.
2. Copied the greeter.proto.ts file from "loopback4-extension-grpc/fixtures/greeter.proto.ts" to my above application.
3. When I run "$npm start", it does not throw any error but the command prompt returns and server is not listening to any specific port.

# Additional information
1. How can I make the client application to call this server?
2. How can I extend this to make grpc stream calls between client and server on loopback 4.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the scaffolded app's Index.ts and the Component Configuration section of @loopback/grpc. Compare the setup with loopback4-extension-grpc/fixtures/greeter.proto.ts, then run npm start to reproduce the missing generated file and server listener. Done means the proto TypeScript file is generated and the server listens on its configured port.

Written by the indexing model from the issue text.

Assessment

Tech stack
grpc, typescript
Domain
api, backend
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.