feat: move from grpc to @grpc/grpc-js #4806
Merged
Conversation
1bcaf2a
to
4889cd5
@tonivj5 I have problems with tests... can you help me? |
I don't know what happens and Circle CI logs aren't public, I can't check it either... Wait the reply of some maintainer, it will come! |
3 tasks
1 task
Pull Request Test Coverage Report for Build 208e1d5f-fc96-4c3f-95c9-1c6986ba55dd
|
b8d0f67
to
6a2ba31
thanks to @LastKing for solving tests issues... please @kamilmysliwiec review this when you have some time |
build: update package dependencies fix: use bindAsync in server-grpc test(): server gprc port already listen error test(): remove surplus commit feat: fix packages # Conflicts: # package-lock.json # package.json # sample/04-grpc/package-lock.json # sample/04-grpc/package.json
any particular reason why this PR is blocked? |
This PR introduces a breaking change. It won't be merged till the next major release. |
1 task
1 task
1 task
1 task
1 task
1 task
1 task
1 task
1 task
1 task
1 task
1 task
1 task
1 task
1 task
1 task
1 task
1 task
1 task
1 task
1 task
1 task
1 task
1 task
1 task
1 task
1 task
1 task
1 task
1 task
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
PR Checklist
Please check if your PR fulfills the following requirements:
PR Type
What kind of change does this PR introduce?
What is the current behavior?
Issue Number: #4799
What is the new behavior?
Does this PR introduce a breaking change?
a new package should be installed:
@grpc/grpc-js
Other information
The text was updated successfully, but these errors were encountered: