Improve error handling on Authproto

[essential-randomness]

Supercedes #12

[siotle]

Looks good to me!
although, hm, not sure what happened to package-lock.json.

[essential-randomness]

Looks good to me! although, hm, not sure what happened to package-lock.json.

(Assuming this is what you're asking) When you run npm install it will update the dependencies in package-lock.json to the most recent versions that are compatible with what you have already installed. To avoid that one should npm ci instead (which, tbh, I maybe should start doing).

[siotle]

Looks good to me! although, hm, not sure what happened to package-lock.json.

(Assuming this is what you're asking) When you run npm install it will update the dependencies in package-lock.json to the most recent versions that are compatible with what you have already installed. To avoid that one should npm ci instead (which, tbh, I maybe should start doing).

I understand that, it's just I'm not sure how we ended up in the position where package-lock.json has to be manually fixed again.

[essential-randomness]

I don't remember a lot about this branch, but generally what happens is:

1. PR#1 comes in with an updated package-lock.json
2. PR#2 comes in with an updated package-lock.json
3. PR#1 (and its package-lock.json) gets merged into main
4. PR#2's package-lock.json now conflicts with the one on main

Every time a new package-lock.json hits main, it's likely to conflict with the ones from open PRs because the dependencies versions within have a tendency to change in incompatible ways. The solution would really be to only commit intentional changes to it.