From 005f06abdb1f648bfb00aa7d6b1f143d103505dd Mon Sep 17 00:00:00 2001 From: alex Date: Tue, 22 Sep 2026 03:24:57 +0300 Subject: [PATCH] Export the release paths so a node10 resolver can read them TypeScript under moduleResolution node10 reads no exports map, and ts-jest falls back to it, so a consumer that imports an artifact subpath fails to compile while the same import runs fine under Node. Rather than have each workspace work around its test runner, the package now also exports releases/* by its own path, which both resolvers accept. Bump npm to 0.2.0 alongside the gem. Co-authored-by: Cursor --- README.md | 14 ++++++++++---- package.json | 3 ++- 2 files changed, 12 insertions(+), 5 deletions(-) diff --git a/README.md b/README.md index 52996e7..e75340c 100644 --- a/README.md +++ b/README.md @@ -39,6 +39,12 @@ Available exports: | `/v5/artifacts/.json` | ABI, creation code, runtime code, immutable slots | | `/v5/abis/.json` | Per-contract ABI | | `/v5/verification-source-codes.json` | solc standard-json input | +| `/releases//...` | The same files, by their path in the package | + +The `/releases/...` paths read the same files as the named exports. They are +there for a toolchain that resolves by file path and reads no `exports` map, +such as TypeScript under `moduleResolution: node10`. Prefer the named exports +where the toolchain supports them. `manifest.json` also lists `callSurfaces`. The token forwards unknown selectors into its extensions, so a client that talks to the token address needs the @@ -46,10 +52,10 @@ merged ABI, not the token ABI alone. ## Ruby -The [`upsideos_evm_rwa_artifacts`](./packages/ruby) gem carries the same ABIs and -verification sources, built from the same audited commit. It ships no bytecode -and no tooling, because a Ruby consumer reads contracts and verifies them but -does not deploy them. +The [`upsideos_evm_rwa_artifacts`](./packages/ruby) gem carries the same ABIs, +creation code and verification sources, built from the same audited commit. It +ships no tooling, because a Ruby consumer reads contracts and hands them on but +does not compile them. ```ruby require 'upsideos_evm_rwa_artifacts' diff --git a/package.json b/package.json index 59e2588..62ca7fe 100644 --- a/package.json +++ b/package.json @@ -1,6 +1,6 @@ { "name": "@upsideos/evm-rwa-artifacts", - "version": "0.1.1", + "version": "0.2.0", "description": "Audited EVM Security Token bytecode, ABIs, and verification sources", "keywords": [ "ethereum", @@ -53,6 +53,7 @@ "./recallable-payment/artifacts/*.json": "./releases/recallable-payment/artifacts/*.json", "./recallable-payment/abis/*.json": "./releases/recallable-payment/abi/*.json", "./recallable-payment/verification-source-codes.json": "./releases/recallable-payment/verification-source-codes.json", + "./releases/*": "./releases/*", "./package.json": "./package.json" }, "scripts": {