upgrade grpc-js

[Feiyang1]

Fixes #3196

Changed it to ^1.0.0. @schmidt-sebastian Are you comfortable with the caret range? Does grpc-js follow semver?

[google-oss-bot]

Binary Size Report

Affected SDKs

No changes between base commit (1e3721c) and head commit (b9db2a3).

Test Logs

• Base (1e3721c5): https://github.com/firebase/firebase-js-sdk/actions/runs/130327286
• Head (b9db2a30): https://github.com/firebase/firebase-js-sdk/actions/runs/131272990

[schmidt-sebastian]

Looks like GitHub ate my comment again:

• grpc-js follows semver.
• I think we should update.
• I think this addresses Emulator Firestore: Channel credentials must be a ChannelCredentials object #3196 but doesn't fix Emulator Firestore: Channel credentials must be a ChannelCredentials object #3196, as versions might still be pinned incorrectly for users with package-lock.json files. I think we should pass in our grpc client to firebase-admin (will work on that today). If that works, we can probably pin grpc-js to a specific version in our repo to match the existing pattern in our SDk.

[Feiyang1]

If that works, we can probably pin grpc-js to a specific version in our repo to match the existing pattern in our SDk.

I actually think we should stop pinning to a specific version for external dependencies (non-@firebase dependencies), because otherwise it leads to package fragmentation problem seen in #3196 and #3031

Though we will lose some control on our dependencies, but if they follow semver, we will probably be fine.

So if you are comfortable with ^ range, I think we should use it.