mirror of https://github.com/grpc/grpc-node.git
grpc-js: Add "Migrating from grpc" README section
This commit is contained in:
parent
5df87c9ac9
commit
615058036b
|
|
@ -21,9 +21,16 @@ npm install @grpc/grpc-js
|
|||
- Connection Keepalives
|
||||
- HTTP Connect support (proxies)
|
||||
|
||||
|
||||
This library does not directly handle `.proto` files. To use `.proto` files with this library we recommend using the `@grpc/proto-loader` package.
|
||||
|
||||
## Migrating from [`grpc`](https://www.npmjs.com/package/grpc)
|
||||
|
||||
`@grpc/grpc-js` is almost a drop-in replacement for `grpc`, but you may need to make a few code changes to use it:
|
||||
|
||||
- If you are currently loading `.proto` files using `grpc.load`, that function is not available in this library. You should instead load your `.proto` files using `@grpc/proto-loader` and load the resulting package definition objects into `@grpc/grpc-js` using `grpc.loadPackageDefinition`.
|
||||
- If you are currently loading packages generated by `grpc-tools`, you should instead generate your files using the `--generate_package_definitions` option in `grpc-tools`, then load the object exported by the generated file into `@grpc/grpc-js` using `grpc.loadPackageDefinition`.
|
||||
- If you have a server and you are using `Server#bind` to bind ports, you will need to use `Server#bindAsync` instead.
|
||||
|
||||
## Some Notes on API Guarantees
|
||||
|
||||
The public API of this library follows semantic versioning, with some caveats:
|
||||
|
|
|
|||
Loading…
Reference in New Issue