Agent-JS 0.21.2

[anon74414410]

The latest release for agent-js is here with a few new features to be aware of!

We have a fix for the disableIdle flag, we’ve swapped secp256k1 for @noble/curves/secp256k1, and there’s a new PartialIdentity export in @dfinity/identity that you can use in @dfinity/auth-client to delegate to any public key without needing to have the full key pair available in the Agent.

What’s Changed

• fix: running audit fix by @krpeacock in #826
• fix: honor disableIdle flag by @ncpenke in #809
• fix: Limit the delegation depth of read_state certificates to 1 by @oggy-dfin in #813
• chore(deps-dev): bump vite from 4.5.0 to 5.0.5 by @dependabot in #810
• feat: introduces partial identity by @krpeacock in #812
• feat: replaces secp256k1 npm package with @noble/curves by @krpeacock in #814
• chore: GitHub actions warning cleanup by @krpeacock in #819
• chore: cleaning up linting and stricter CI by @krpeacock in #821
• feat: add github.dev and gitpod.io to known hosts by @rvanasa in #822

Release Release 0.21.2 · dfinity/icp-js-core

P.S. We’re trying out a new publishing process, so apologies for the unnecessary patches while we get the process smoothed out!

[cryptoschindler]

i see that @rvanasa added gitpod.io to the known hosts again, but something broke between 0.18.1 and and this release. using the default actor exported from the generated declarations, the request url changed between the versions. the new path doesn’t work for gitpod.

0.18.1 path on gitpod

0.21.2 path on gitpod

[cryptoschindler]

this should probably be hostname instead of knownHost, at least for the gitpod usecase

[rvanasa]

You’re right; thanks for catching this. Follow-up PR: #830

[anon74414410]

@cryptoschindler I’ll get a patch out for this soon!

[cryptoschindler]

This has been patched

[cryptoschindler]

@anon74414410 @rvanasa
I was wondering, could there be a similar approach for authClient.login? That is I can omit the identityProvider key and the authClient will figure out the correct provider URL on my behalf. If not, how would you implement an identityProvider that works locally, on mainnet and in environments like github.dev and gitpod.io?

currently i’m just using this

			// start the login process and wait for it to finish
			await new Promise<void>((resolve, reject) => {
				authClient.login({
					identityProvider:
						process.env.DFX_NETWORK === 'ic'
							? 'https://identity.ic0.app'
							: `http://rdmx6-jaaaa-aaaaa-aaadq-cai.localhost:4943`,
					onSuccess: resolve,
					onError: reject,
					windowOpenerFeatures: `toolbar=0,location=0,menubar=0,width=400,height=600,left=${window.screen.width / 2 - 200},top=${window.screen.height / 2 - 300}`
				});
			});

[anon74414410]

My view is that trying to make inferring idpProvider work isn’t worth it. There are a dozen ways someone might want to pass the configuration - global variable, url parameter, environment variable, etc. host is special because you can point at "/", but idpProvider will always be a separate domain.