feat(api): update via SDK Studio

.stats.yml

@@ -1,2 +1,2 @@
 configured_endpoints: 12
-openapi_spec_url: https://storage.googleapis.com/stainless-sdk-openapi-specs/maestro%2Fmaestro-arch-rpc-a04ce538c803bb8fd64c905a15cf7a02063faa72addd34cb7f31086f434fa666.yml
+openapi_spec_url: https://storage.googleapis.com/stainless-sdk-openapi-specs/maestro%2Fmaestro-arch-rpc-8a4099d01f990ae9bca950c4779cb86460aafd58569bd1cb975bfba53d47e347.yml

CONTRIBUTING.md

@@ -42,25 +42,25 @@ If you’d like to use the repository from source, you can either install from g
 To install via git:
 
 ```sh
-$ npm install git+ssh://[email protected]:maestro-org/maestro-arch-rpc-node-sdk.git
+$ npm install git+ssh://[email protected]:stainless-sdks/maestro-arch-rpc-node.git
 ```
 
 Alternatively, to link a local copy of the repo:
 
 ```sh
 # Clone
-$ git clone https://www.github.com/maestro-org/maestro-arch-rpc-node-sdk
-$ cd maestro-arch-rpc-node-sdk
+$ git clone https://www.github.com/stainless-sdks/maestro-arch-rpc-node
+$ cd maestro-arch-rpc-node
 
 # With yarn
 $ yarn link
 $ cd ../my-package
-$ yarn link maestro-arch-rpc-sdk
+$ yarn link maestro-arch-rpc
 
 # With pnpm
 $ pnpm link --global
 $ cd ../my-package
-$ pnpm link -—global maestro-arch-rpc-sdk
+$ pnpm link -—global maestro-arch-rpc
 ```
 
 ## Running tests
@@ -99,7 +99,7 @@ the changes aren't made through the automated pipeline, you may want to make rel
 
 ### Publish with a GitHub workflow
 
-You can release to package managers by using [the `Publish NPM` GitHub action](https://www.github.com/maestro-org/maestro-arch-rpc-node-sdk/actions/workflows/publish-npm.yml). This requires a setup organization or repository secret to be set up.
+You can release to package managers by using [the `Publish NPM` GitHub action](https://www.github.com/stainless-sdks/maestro-arch-rpc-node/actions/workflows/publish-npm.yml). This requires a setup organization or repository secret to be set up.
 
 ### Publish manually
 

README.md

@@ -1,6 +1,6 @@
 # Maestro Arch Rpc Node API Library
 
-[![NPM version](https://img.shields.io/npm/v/maestro-arch-rpc-sdk.svg)](https://npmjs.org/package/maestro-arch-rpc-sdk) ![npm bundle size](https://img.shields.io/bundlephobia/minzip/maestro-arch-rpc-sdk)
+[![NPM version](https://img.shields.io/npm/v/maestro-arch-rpc.svg)](https://npmjs.org/package/maestro-arch-rpc) ![npm bundle size](https://img.shields.io/bundlephobia/minzip/maestro-arch-rpc)
 
 This library provides convenient access to the Maestro Arch Rpc REST API from server-side TypeScript or JavaScript.
 
@@ -11,16 +11,19 @@ It is generated with [Stainless](https://www.stainlessapi.com/).
 ## Installation
 
 ```sh
-npm install maestro-arch-rpc-sdk
+npm install git+ssh://[email protected]:stainless-sdks/maestro-arch-rpc-node.git
 ```
 
+> [!NOTE]
+> Once this package is [published to npm](https://app.stainlessapi.com/docs/guides/publish), this will become: `npm install maestro-arch-rpc`
+
 ## Usage
 
 The full API of this library can be found in [api.md](api.md).
 
 <!-- prettier-ignore -->
 ```js
-import MaestroArchRpc from 'maestro-arch-rpc-sdk';
+import MaestroArchRpc from 'maestro-arch-rpc';
 
 const client = new MaestroArchRpc();
 
@@ -39,7 +42,7 @@ This library includes TypeScript definitions for all request params and response
 
 <!-- prettier-ignore -->
 ```ts
-import MaestroArchRpc from 'maestro-arch-rpc-sdk';
+import MaestroArchRpc from 'maestro-arch-rpc';
 
 const client = new MaestroArchRpc();
 
@@ -207,12 +210,12 @@ add the following import before your first import `from "MaestroArchRpc"`:
 ```ts
 // Tell TypeScript and the package to use the global web fetch instead of node-fetch.
 // Note, despite the name, this does not add any polyfills, but expects them to be provided if needed.
-import 'maestro-arch-rpc-sdk/shims/web';
-import MaestroArchRpc from 'maestro-arch-rpc-sdk';
+import 'maestro-arch-rpc/shims/web';
+import MaestroArchRpc from 'maestro-arch-rpc';
 ```
 
-To do the inverse, add `import "maestro-arch-rpc-sdk/shims/node"` (which does import polyfills).
-This can also be useful if you are getting the wrong TypeScript types for `Response` ([more details](https://github.com/maestro-org/maestro-arch-rpc-node-sdk/tree/main/src/_shims#readme)).
+To do the inverse, add `import "maestro-arch-rpc/shims/node"` (which does import polyfills).
+This can also be useful if you are getting the wrong TypeScript types for `Response` ([more details](https://github.com/stainless-sdks/maestro-arch-rpc-node/tree/main/src/_shims#readme)).
 
 ### Logging and middleware
 
@@ -221,7 +224,7 @@ which can be used to inspect or alter the `Request` or `Response` before/after e
 
 ```ts
 import { fetch } from 'undici'; // as one example
-import MaestroArchRpc from 'maestro-arch-rpc-sdk';
+import MaestroArchRpc from 'maestro-arch-rpc';
 
 const client = new MaestroArchRpc({
   fetch: async (url: RequestInfo, init?: RequestInit): Promise<Response> => {
@@ -268,7 +271,7 @@ This package generally follows [SemVer](https://semver.org/spec/v2.0.0.html) con
 
 We take backwards-compatibility seriously and work hard to ensure you can rely on a smooth upgrade experience.
 
-We are keen for your feedback; please open an [issue](https://www.github.com/maestro-org/maestro-arch-rpc-node-sdk/issues) with questions, bugs, or suggestions.
+We are keen for your feedback; please open an [issue](https://www.github.com/stainless-sdks/maestro-arch-rpc-node/issues) with questions, bugs, or suggestions.
 
 ## Requirements
 

jest.config.ts

@@ -7,9 +7,9 @@ const config: JestConfigWithTsJest = {
     '^.+\\.(t|j)sx?$': ['@swc/jest', { sourceMaps: 'inline' }],
   },
   moduleNameMapper: {
-    '^maestro-arch-rpc-sdk$': '<rootDir>/src/index.ts',
-    '^maestro-arch-rpc-sdk/_shims/auto/(.*)$': '<rootDir>/src/_shims/auto/$1-node',
-    '^maestro-arch-rpc-sdk/(.*)$': '<rootDir>/src/$1',
+    '^maestro-arch-rpc$': '<rootDir>/src/index.ts',
+    '^maestro-arch-rpc/_shims/auto/(.*)$': '<rootDir>/src/_shims/auto/$1-node',
+    '^maestro-arch-rpc/(.*)$': '<rootDir>/src/$1',
   },
   modulePathIgnorePatterns: [
     '<rootDir>/ecosystem-tests/',

package.json

@@ -1,12 +1,12 @@
 {
-  "name": "maestro-arch-rpc-sdk",
+  "name": "maestro-arch-rpc",
   "version": "0.0.1-alpha.1",
   "description": "The official TypeScript library for the Maestro Arch Rpc API",
   "author": "Maestro Arch Rpc <[email protected]>",
   "types": "dist/index.d.ts",
   "main": "dist/index.js",
   "type": "commonjs",
-  "repository": "github:maestro-org/maestro-arch-rpc-node-sdk",
+  "repository": "github:stainless-sdks/maestro-arch-rpc-node",
   "license": "Apache-2.0",
   "packageManager": "[email protected]",
   "files": [
@@ -60,8 +60,8 @@
     "./shims/web.mjs"
   ],
   "imports": {
-    "maestro-arch-rpc-sdk": ".",
-    "maestro-arch-rpc-sdk/*": "./src/*"
+    "maestro-arch-rpc": ".",
+    "maestro-arch-rpc/*": "./src/*"
   },
   "exports": {
     "./_shims/auto/*": {

scripts/build

@@ -8,7 +8,7 @@ node scripts/utils/check-version.cjs
 
 # Build into dist and will publish the package from there,
 # so that src/resources/foo.ts becomes <package root>/resources/foo.js
-# This way importing from `"maestro-arch-rpc-sdk/resources/foo"` works
+# This way importing from `"maestro-arch-rpc/resources/foo"` works
 # even with `"moduleResolution": "node"`
 
 rm -rf dist; mkdir dist
@@ -47,8 +47,8 @@ node scripts/utils/postprocess-files.cjs
 
 # make sure that nothing crashes when we require the output CJS or
 # import the output ESM
-(cd dist && node -e 'require("maestro-arch-rpc-sdk")')
-(cd dist && node -e 'import("maestro-arch-rpc-sdk")' --input-type=module)
+(cd dist && node -e 'require("maestro-arch-rpc")')
+(cd dist && node -e 'import("maestro-arch-rpc")' --input-type=module)
 
 if command -v deno &> /dev/null && [ -e ./scripts/build-deno ]
 then

scripts/utils/postprocess-files.cjs

@@ -2,7 +2,7 @@ const fs = require('fs');
 const path = require('path');
 const { parse } = require('@typescript-eslint/parser');
 
-const pkgImportPath = process.env['PKG_IMPORT_PATH'] ?? 'maestro-arch-rpc-sdk/';
+const pkgImportPath = process.env['PKG_IMPORT_PATH'] ?? 'maestro-arch-rpc/';
 
 const distDir =
   process.env['DIST_PATH'] ?
@@ -142,7 +142,7 @@ async function postprocess() {
 
     if (file.endsWith('.d.ts')) {
       // work around bad tsc behavior
-      // if we have `import { type Readable } from 'maestro-arch-rpc-sdk/_shims/index'`,
+      // if we have `import { type Readable } from 'maestro-arch-rpc/_shims/index'`,
       // tsc sometimes replaces `Readable` with `import("stream").Readable` inline
       // in the output .d.ts
       transformed = transformed.replace(/import\("stream"\).Readable/g, 'Readable');

src/_shims/README.md

@@ -1,9 +1,9 @@
 # 👋 Wondering what everything in here does?
 
-`maestro-arch-rpc-sdk` supports a wide variety of runtime environments like Node.js, Deno, Bun, browsers, and various
+`maestro-arch-rpc` supports a wide variety of runtime environments like Node.js, Deno, Bun, browsers, and various
 edge runtimes, as well as both CommonJS (CJS) and EcmaScript Modules (ESM).
 
-To do this, `maestro-arch-rpc-sdk` provides shims for either using `node-fetch` when in Node (because `fetch` is still experimental there) or the global `fetch` API built into the environment when not in Node.
+To do this, `maestro-arch-rpc` provides shims for either using `node-fetch` when in Node (because `fetch` is still experimental there) or the global `fetch` API built into the environment when not in Node.
 
 It uses [conditional exports](https://nodejs.org/api/packages.html#conditional-exports) to
 automatically select the correct shims for each environment. However, conditional exports are a fairly new
@@ -15,32 +15,32 @@ getting the wrong raw `Response` type from `.asResponse()`, for example.
 
 The user can work around these issues by manually importing one of:
 
-- `import 'maestro-arch-rpc-sdk/shims/node'`
-- `import 'maestro-arch-rpc-sdk/shims/web'`
+- `import 'maestro-arch-rpc/shims/node'`
+- `import 'maestro-arch-rpc/shims/web'`
 
 All of the code here in `_shims` handles selecting the automatic default shims or manual overrides.
 
 ### How it works - Runtime
 
-Runtime shims get installed by calling `setShims` exported by `maestro-arch-rpc-sdk/_shims/registry`.
+Runtime shims get installed by calling `setShims` exported by `maestro-arch-rpc/_shims/registry`.
 
-Manually importing `maestro-arch-rpc-sdk/shims/node` or `maestro-arch-rpc-sdk/shims/web`, calls `setShims` with the respective runtime shims.
+Manually importing `maestro-arch-rpc/shims/node` or `maestro-arch-rpc/shims/web`, calls `setShims` with the respective runtime shims.
 
-All client code imports shims from `maestro-arch-rpc-sdk/_shims/index`, which:
+All client code imports shims from `maestro-arch-rpc/_shims/index`, which:
 
 - checks if shims have been set manually
-- if not, calls `setShims` with the shims from `maestro-arch-rpc-sdk/_shims/auto/runtime`
-- re-exports the installed shims from `maestro-arch-rpc-sdk/_shims/registry`.
+- if not, calls `setShims` with the shims from `maestro-arch-rpc/_shims/auto/runtime`
+- re-exports the installed shims from `maestro-arch-rpc/_shims/registry`.
 
-`maestro-arch-rpc-sdk/_shims/auto/runtime` exports web runtime shims.
-If the `node` export condition is set, the export map replaces it with `maestro-arch-rpc-sdk/_shims/auto/runtime-node`.
+`maestro-arch-rpc/_shims/auto/runtime` exports web runtime shims.
+If the `node` export condition is set, the export map replaces it with `maestro-arch-rpc/_shims/auto/runtime-node`.
 
 ### How it works - Type time
 
-All client code imports shim types from `maestro-arch-rpc-sdk/_shims/index`, which selects the manual types from `maestro-arch-rpc-sdk/_shims/manual-types` if they have been declared, otherwise it exports the auto types from `maestro-arch-rpc-sdk/_shims/auto/types`.
+All client code imports shim types from `maestro-arch-rpc/_shims/index`, which selects the manual types from `maestro-arch-rpc/_shims/manual-types` if they have been declared, otherwise it exports the auto types from `maestro-arch-rpc/_shims/auto/types`.
 
-`maestro-arch-rpc-sdk/_shims/manual-types` exports an empty namespace.
-Manually importing `maestro-arch-rpc-sdk/shims/node` or `maestro-arch-rpc-sdk/shims/web` merges declarations into this empty namespace, so they get picked up by `maestro-arch-rpc-sdk/_shims/index`.
+`maestro-arch-rpc/_shims/manual-types` exports an empty namespace.
+Manually importing `maestro-arch-rpc/shims/node` or `maestro-arch-rpc/shims/web` merges declarations into this empty namespace, so they get picked up by `maestro-arch-rpc/_shims/index`.
 
-`maestro-arch-rpc-sdk/_shims/auto/types` exports web type definitions.
-If the `node` export condition is set, the export map replaces it with `maestro-arch-rpc-sdk/_shims/auto/types-node`, though TS only picks this up if `"moduleResolution": "nodenext"` or `"moduleResolution": "bundler"`.
+`maestro-arch-rpc/_shims/auto/types` exports web type definitions.
+If the `node` export condition is set, the export map replaces it with `maestro-arch-rpc/_shims/auto/types-node`, though TS only picks this up if `"moduleResolution": "nodenext"` or `"moduleResolution": "bundler"`.

src/_shims/index-deno.ts

@@ -79,7 +79,7 @@ export function getDefaultAgent(url: string) {
 }
 export function fileFromPath() {
   throw new Error(
-    'The `fileFromPath` function is only supported in Node. See the README for more details: https://www.github.com/maestro-org/maestro-arch-rpc-node-sdk#file-uploads',
+    'The `fileFromPath` function is only supported in Node. See the README for more details: https://www.github.com/stainless-sdks/maestro-arch-rpc-node#file-uploads',
   );
 }
 

src/_shims/index.d.ts

@@ -2,7 +2,7 @@
  * Disclaimer: modules in _shims aren't intended to be imported by SDK users.
  */
 import { manual } from './manual-types';
-import * as auto from 'maestro-arch-rpc-sdk/_shims/auto/types';
+import * as auto from 'maestro-arch-rpc/_shims/auto/types';
 import { type RequestOptions } from '../core';
 
 type SelectType<Manual, Auto> = unknown extends Manual ? Auto : Manual;

src/_shims/index.js

@@ -2,7 +2,7 @@
  * Disclaimer: modules in _shims aren't intended to be imported by SDK users.
  */
 const shims = require('./registry');
-const auto = require('maestro-arch-rpc-sdk/_shims/auto/runtime');
+const auto = require('maestro-arch-rpc/_shims/auto/runtime');
 if (!shims.kind) shims.setShims(auto.getRuntime(), { auto: true });
 for (const property of Object.keys(shims)) {
   Object.defineProperty(exports, property, {

src/_shims/index.mjs

@@ -2,6 +2,6 @@
  * Disclaimer: modules in _shims aren't intended to be imported by SDK users.
  */
 import * as shims from './registry.mjs';
-import * as auto from 'maestro-arch-rpc-sdk/_shims/auto/runtime';
+import * as auto from 'maestro-arch-rpc/_shims/auto/runtime';
 if (!shims.kind) shims.setShims(auto.getRuntime(), { auto: true });
 export * from './registry.mjs';

src/_shims/manual-types.d.ts

@@ -4,8 +4,8 @@
 /**
  * Types will get added to this namespace when you import one of the following:
  *
- *   import 'maestro-arch-rpc-sdk/shims/node'
- *   import 'maestro-arch-rpc-sdk/shims/web'
+ *   import 'maestro-arch-rpc/shims/node'
+ *   import 'maestro-arch-rpc/shims/web'
  *
  * Importing more than one will cause type and runtime errors.
  */

src/_shims/registry.ts

@@ -42,12 +42,12 @@ export let isFsReadStream: Shims['isFsReadStream'] | undefined = undefined;
 export function setShims(shims: Shims, options: { auto: boolean } = { auto: false }) {
   if (auto) {
     throw new Error(
-      `you must \`import 'maestro-arch-rpc-sdk/shims/${shims.kind}'\` before importing anything else from maestro-arch-rpc-sdk`,
+      `you must \`import 'maestro-arch-rpc/shims/${shims.kind}'\` before importing anything else from maestro-arch-rpc`,
     );
   }
   if (kind) {
     throw new Error(
-      `can't \`import 'maestro-arch-rpc-sdk/shims/${shims.kind}'\` after \`import 'maestro-arch-rpc-sdk/shims/${kind}'\``,
+      `can't \`import 'maestro-arch-rpc/shims/${shims.kind}'\` after \`import 'maestro-arch-rpc/shims/${kind}'\``,
     );
   }
   auto = options.auto;

src/_shims/web-runtime.ts

@@ -9,9 +9,9 @@ export function getRuntime({ manuallyImported }: { manuallyImported?: boolean }
   const recommendation =
     manuallyImported ?
       `You may need to use polyfills`
-    : `Add one of these imports before your first \`import … from 'maestro-arch-rpc-sdk'\`:
-- \`import 'maestro-arch-rpc-sdk/shims/node'\` (if you're running on Node)
-- \`import 'maestro-arch-rpc-sdk/shims/web'\` (otherwise)
+    : `Add one of these imports before your first \`import … from 'maestro-arch-rpc'\`:
+- \`import 'maestro-arch-rpc/shims/node'\` (if you're running on Node)
+- \`import 'maestro-arch-rpc/shims/web'\` (otherwise)
 `;
 
   let _fetch, _Request, _Response, _Headers;
@@ -95,7 +95,7 @@ export function getRuntime({ manuallyImported }: { manuallyImported?: boolean }
     getDefaultAgent: (url: string) => undefined,
     fileFromPath: () => {
       throw new Error(
-        'The `fileFromPath` function is only supported in Node. See the README for more details: https://www.github.com/maestro-org/maestro-arch-rpc-node-sdk#file-uploads',
+        'The `fileFromPath` function is only supported in Node. See the README for more details: https://www.github.com/stainless-sdks/maestro-arch-rpc-node#file-uploads',
       );
     },
     isFsReadStream: (value: any) => false,

src/core.ts

@@ -99,9 +99,9 @@ export class APIPromise<T> extends Promise<T> {
    *
    * 👋 Getting the wrong TypeScript type for `Response`?
    * Try setting `"moduleResolution": "NodeNext"` if you can,
-   * or add one of these imports before your first `import … from 'maestro-arch-rpc-sdk'`:
-   * - `import 'maestro-arch-rpc-sdk/shims/node'` (if you're running on Node)
-   * - `import 'maestro-arch-rpc-sdk/shims/web'` (otherwise)
+   * or add one of these imports before your first `import … from 'maestro-arch-rpc'`:
+   * - `import 'maestro-arch-rpc/shims/node'` (if you're running on Node)
+   * - `import 'maestro-arch-rpc/shims/web'` (otherwise)
    */
   asResponse(): Promise<Response> {
     return this.responsePromise.then((p) => p.response);
@@ -115,9 +115,9 @@ export class APIPromise<T> extends Promise<T> {
    *
    * 👋 Getting the wrong TypeScript type for `Response`?
    * Try setting `"moduleResolution": "NodeNext"` if you can,
-   * or add one of these imports before your first `import … from 'maestro-arch-rpc-sdk'`:
-   * - `import 'maestro-arch-rpc-sdk/shims/node'` (if you're running on Node)
-   * - `import 'maestro-arch-rpc-sdk/shims/web'` (otherwise)
+   * or add one of these imports before your first `import … from 'maestro-arch-rpc'`:
+   * - `import 'maestro-arch-rpc/shims/node'` (if you're running on Node)
+   * - `import 'maestro-arch-rpc/shims/web'` (otherwise)
    */
   async withResponse(): Promise<{ data: T; response: Response }> {
     const [data, response] = await Promise.all([this.parse(), this.asResponse()]);

src/version.ts

@@ -1 +1 @@
-export const VERSION = '0.0.1-alpha.1'; // x-release-please-version
+export const VERSION = '0.0.1-alpha.1';

tests/api-resources/accounts.test.ts

@@ -1,6 +1,6 @@
 // File generated from our OpenAPI spec by Stainless. See CONTRIBUTING.md for details.
 
-import MaestroArchRpc from 'maestro-arch-rpc-sdk';
+import MaestroArchRpc from 'maestro-arch-rpc';
 import { Response } from 'node-fetch';
 
 const client = new MaestroArchRpc({ baseURL: process.env['TEST_API_BASE_URL'] ?? 'http://127.0.0.1:4010' });

tests/api-resources/blocks.test.ts

@@ -1,6 +1,6 @@
 // File generated from our OpenAPI spec by Stainless. See CONTRIBUTING.md for details.
 
-import MaestroArchRpc from 'maestro-arch-rpc-sdk';
+import MaestroArchRpc from 'maestro-arch-rpc';
 import { Response } from 'node-fetch';
 
 const client = new MaestroArchRpc({ baseURL: process.env['TEST_API_BASE_URL'] ?? 'http://127.0.0.1:4010' });

tests/api-resources/programs.test.ts

@@ -1,6 +1,6 @@
 // File generated from our OpenAPI spec by Stainless. See CONTRIBUTING.md for details.
 
-import MaestroArchRpc from 'maestro-arch-rpc-sdk';
+import MaestroArchRpc from 'maestro-arch-rpc';
 import { Response } from 'node-fetch';
 
 const client = new MaestroArchRpc({ baseURL: process.env['TEST_API_BASE_URL'] ?? 'http://127.0.0.1:4010' });

tests/api-resources/transactions.test.ts

@@ -1,6 +1,6 @@
 // File generated from our OpenAPI spec by Stainless. See CONTRIBUTING.md for details.
 
-import MaestroArchRpc from 'maestro-arch-rpc-sdk';
+import MaestroArchRpc from 'maestro-arch-rpc';
 import { Response } from 'node-fetch';
 
 const client = new MaestroArchRpc({ baseURL: process.env['TEST_API_BASE_URL'] ?? 'http://127.0.0.1:4010' });