@Christian Vaagland Tellnes , I am
# spicedb
j
@Christian Vaagland Tellnes , I am seeing the same issue. In the meantime, I've worked around this by pinning
"@grpc/grpc-js": "1.12.6"
in my package.json, until a newer version of the
authzed-node
library is released.
m
Thanks for the info!
c
Thank you. I expected something like this was the solution for a work-around. I've just not put in the effort to debug and figure that out.
For future readers (using Yarn package manager), adding this to my package.json file works around the problem:
Copy code
json
  "resolutions": {
    "@grpc/grpc-js": "1.12.6"
  }
y
good find! i'll see if i can find an associated issue on the grpc-js side
hmm... it does seem as though something changed, but i'm unsure of what. i'm tracking the issue here: https://github.com/authzed/authzed-node/issues/206
v1.2.3 should have a temporary fix for this; i'll fix it more permanently in the fix for the above issue
4 Views