SDK import by module

[wcalderipe]

The SDK's main index.ts file was exporting everything, which led to frequent name clashing issues (e.g., client).

This PR updates the SDK to have modules by path, such as @narval-xyz/armory-sdk/vault or @narval-xyz/armory-sdk/data-source. It also fixes the packages/release target error because it was unable to derive the tag from git.

Another important change was the proxy to signature and policy-engine-shared packages. These are now also exported as modules.

Interface comparison

From

import { getAddress, RsaKey, VaultClient, AuthClient } from '@narval-xyz/armory-sdk'

To

import { VaultClient } from '@narval-xyz/armory-sdk/vault'
import { AuthClient } from '@narval-xyz/armory-sdk/auth'
import { getAddress } from '@narval-xyz/armory-sdk/policy-engine-shared'
import { RsaKey } from '@narval-xyz/armory-sdk/signature'

Why manually move the files from src to the dist's root?

For some reason, I couldn't make it work with the NX release build system when the external option is set to none. As a reminder, the external option is crucial in the build process to bundle the signature and policy-engine-shared into the SDK artifact.

For more information about the external option, see #301.

Why not a major version bump?

The SDK is in its early stages and the interface is also going to evolve quickly in the next month. I'd rather reserve the 1.0.0 for when we have a stable interface.

[wcalderipe]

Blocked by lack of bandwidth at the moment.

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
devtool	❌ Failed (Inspect)			Jul 26, 2024 0:26am

[samteb]

@wcalderipe please check that we are still exposing types from policy-engine-shared and signature packages.

[mattschoch]

I'm going to close this PR; the branch exists if we decide to keep running w/ this, but this PR is getting pretty stale & not imminently going to be addressed.