@murgatroid99 I ended up in one of your github issues earlier today. Was trying to help a friend figure out why his npm install was failing while mine worked fine. Saw your username and avatar and was like "Hey I know that person! They play magic."

And now I'm learning more about gRPC because someone indicated that it might be better than SignalR (which we use)

It's like meeting someone in the grocery store that you know from work

I've also used protobuf and protoc. Maybe that would help make the transition easier

Well where I'm from meeting a coworker around town is not a big deal

This is like meeting a coworker in Dallas I feel like

I'm curious which issue it was that you found

Trying to find it

It was this one: github.com/grpc/grpc-node/issues/888

We never did root cause the issue. We just downgraded his node.js to an earlier version.

Nothing to do with your package by the way. Just happened to have the same error message

It turns out that publishing a native addon that supports Node and/or Electron is a major pain in the ass, in large part because they publish a new major version every 6 months or so

I'm a .NET developer primarily. We use Node for some frontend stuff but we don't deal with it that often so even minor problems can be tricky. It's a pain in the ass for us too.

I wonder what it would be like to use TypeScript for both frontend and backend. Just get good at one language.

Must be fun because TypeScript was high on the dev survey's list of most loved languages

Good luck with your gRPC work. I'm out for now.