Just encountered the same problem. @types/[email protected] is causing an additional Long type that's incompatible with the builtin Long type from [email protected]. Had to add import Long from "long"; to generated proto.d.ts to prevent it from picking up the wrong Long from @types/long.

Well, this happens to be harder than I thought - adding this actually breaks some code that depended on import * as Long from 'long' being possible, so it's a breaking change. I will need to roll it back now and think how we could proceed here.

Maybe not rollback, since we actually have more packages doing the same thing with long, but I'll take some time before releasing that to make sure other code I care about does not break because of this. I expect to release this some time next week.