feat(PLATENG-800): Replace @lifeomic/alpha with @jupiterone/platform-sdk-fetch#1188
feat(PLATENG-800): Replace @lifeomic/alpha with @jupiterone/platform-sdk-fetch#1188tokio-on-jupiter wants to merge 39 commits intomainfrom
Conversation
|
Review the following changes in direct dependencies. Learn more about Socket for GitHub.
|
There was a problem hiding this comment.
Pull request overview
This PR replaces the deprecated @lifeomic/alpha HTTP client with @jupiterone/platform-sdk-fetch canary release to modernize the API client implementation.
Changes:
- Updated dependency from
@lifeomic/alphato@jupiterone/platform-sdk-fetch - Replaced
Alphatype withRequestClientthroughout the codebase - Removed proxy configuration support and deprecated
alphaOptions/proxyUrlparameters
Reviewed changes
Copilot reviewed 9 out of 10 changed files in this pull request and generated 2 comments.
Show a summary per file
| File | Description |
|---|---|
| packages/integration-sdk-runtime/package.json | Updated dependency to platform-sdk-fetch canary |
| packages/integration-sdk-runtime/src/api/index.ts | Replaced Alpha with RequestClient, removed proxy support |
| packages/integration-sdk-runtime/src/synchronization/index.ts | Updated type imports and error handling |
| packages/integration-sdk-runtime/src/synchronization/events.ts | Updated config type imports |
| packages/integration-sdk-runtime/src/synchronization/error.ts | Replaced AxiosError with custom RequestClientError interface |
| packages/integration-sdk-runtime/tsconfig.dist.json | Added skipLibCheck to handle external type issues |
| packages/cli/src/import/importAssetsFromCsv.ts | Updated type imports |
| packages/integration-sdk-runtime/src/api/tests/index.test.ts | Updated mocks for RequestClient |
| packages/cli/src/tests/cli-import.test.ts | Updated test mocks |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
| export const compressRequest: RequestInterceptor = function (config) { | ||
| if ( | ||
| config.method === 'post' && | ||
| config.method === 'POST' && |
There was a problem hiding this comment.
The compressRequest interceptor now only sets the 'Content-Encoding' header but does not actually compress the data. The comment on lines 126-128 notes this issue but doesn't implement actual compression. This means data won't be compressed despite the header claiming it is, which could cause server-side decompression failures.
There was a problem hiding this comment.
This interceptor was removed in a subsequent commit. Compression is now handled directly in `uploadDataChunk()` in `synchronization/index.ts` (lines 537-547), where `gzipData(data)` compresses the payload and sends it via `rawBody` with the `Content-Encoding: gzip` header. The interceptor approach was replaced because `RequestClient` handles request config differently than Alpha.
| @@ -23,7 +35,7 @@ export function synchronizationApiError( | |||
| return new IntegrationError({ | |||
| code: 'UNEXPECTED_SYNCRONIZATION_ERROR', | |||
There was a problem hiding this comment.
Corrected spelling of 'SYNCRONIZATION' to 'SYNCHRONIZATION'.
| code: 'UNEXPECTED_SYNCRONIZATION_ERROR', | |
| code: 'UNEXPECTED_SYNCHRONIZATION_ERROR', |
| 'Content-Encoding': 'gzip', | ||
| }; | ||
| } | ||
| config.data = await gzipData(config.data); |
There was a problem hiding this comment.
Does config.data need to be compressed here?
There was a problem hiding this comment.
This comment is on a deleted line. I'm not sure what action should be taken.
There was a problem hiding this comment.
The compression interceptor was intentionally removed from createApiClient. Compression is now handled directly in uploadDataChunk() (synchronization/index.ts:537-547) where gzipData(data) compresses the payload and sends it via rawBody with the Content-Encoding: gzip header. This approach is more explicit — compression happens at the upload call site rather than as an opaque interceptor.
There was a problem hiding this comment.
No action needed — this was a deleted line from the old Alpha import.
|
/canary-release |
| export const getAccountFromEnvironment = () => | ||
| getFromEnv('JUPITERONE_ACCOUNT', IntegrationAccountRequiredError); | ||
|
|
||
| function parseProxyUrl(proxyUrl: string) { |
There was a problem hiding this comment.
Does the proxy support need to be maintained?
There was a problem hiding this comment.
The comment above suggests that proxy support can still be achieved by setting the HTTPS_PROXY environment variable. I'm not sure if that's true, though. I didn't see any tests that covered that scenario.
There was a problem hiding this comment.
Proxy support was specific to @lifeomic/alpha's internal HTTP client. RequestClient from platform-sdk-fetch does not have built-in proxy configuration — it relies on environment-level proxy settings (e.g. HTTPS_PROXY, HTTP_PROXY) which Node.js and the underlying HTTP client respect natively.
The proxyUrl param is kept in the interface for backward compatibility but now emits a DeprecationWarning when provided, directing users to use environment variables instead. This avoids a breaking change for callers that pass proxyUrl while making it clear the option no longer has any effect.
|
/canary-release |
There was a problem hiding this comment.
Pull request overview
Copilot reviewed 10 out of 11 changed files in this pull request and generated 3 comments.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
| export const compressRequest: RequestInterceptor = function (config) { | ||
| if ( | ||
| config.method === 'post' && | ||
| config.method === 'POST' && | ||
| config.url && | ||
| /\/persister\/synchronization\/jobs\/[0-9a-fA-F-]+\/(entities|relationships)/.test( | ||
| config.url, | ||
| ) | ||
| ) { | ||
| if (config.headers) { | ||
| config.headers['Content-Encoding'] = 'gzip'; | ||
| } else { | ||
| config.headers = { | ||
| // Note: Compression is handled differently in RequestClient | ||
| // The data compression would need to be applied at the request level | ||
| // For now, we mark the headers - actual compression may need additional handling | ||
| return { | ||
| ...config, | ||
| headers: { | ||
| ...config.headers, | ||
| 'Content-Encoding': 'gzip', | ||
| }; | ||
| } | ||
| config.data = await gzipData(config.data); | ||
| }, | ||
| }; | ||
| } | ||
| return config; |
There was a problem hiding this comment.
The compressRequest interceptor sets the 'Content-Encoding: gzip' header but does not actually compress the data. The previous implementation called gzipData(config.data) but this logic has been removed. This will cause the server to expect compressed data but receive uncompressed data, resulting in decompression failures. Either implement the actual data compression using gzipData or remove this interceptor entirely if compression is handled elsewhere.
| code: 'UNEXPECTED_SYNCRONIZATION_ERROR', | ||
| message: errorMessage, | ||
| cause: err, | ||
| cause: err instanceof Error ? err : undefined, |
There was a problem hiding this comment.
Setting cause to undefined when the error is not an instance of Error loses error information. The original implementation passed err directly to preserve all error details. Consider using cause: err as Error or structuring the error differently to retain the original error object for debugging purposes.
| cause: err instanceof Error ? err : undefined, | |
| cause: err as Error, |
There was a problem hiding this comment.
Fixed — now wraps non-Error objects with `new Error(String(err))` instead of discarding them. This preserves the error context for debugging while satisfying the `Error` type requirement for `cause`.
| }); | ||
|
|
||
| describe('getApiKeyFromEnvironment', () => { | ||
| describe('getAccountFromEnvironment', () => { |
There was a problem hiding this comment.
The describe block name 'getAccountFromEnvironment' is a duplicate of line 55's describe block name which should be 'getApiKeyFromEnvironment'. This appears to be a copy-paste error from the original code that should be corrected for clarity.
There was a problem hiding this comment.
This is not a copy-paste error. Line 53 is `getApiKeyFromEnvironment` (tests for `JUPITERONE_API_KEY`) and line 76 is `getAccountFromEnvironment` (tests for `JUPITERONE_ACCOUNT`). They are two separate describe blocks for two different exported functions.
There was a problem hiding this comment.
Pull request overview
Copilot reviewed 10 out of 11 changed files in this pull request and generated 3 comments.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
| /** | ||
| * Request interceptor that compresses upload data for synchronization endpoints | ||
| */ | ||
| export const compressRequest: RequestInterceptor = function (config) { | ||
| if ( | ||
| config.method === 'post' && | ||
| config.method === 'POST' && | ||
| config.url && | ||
| /\/persister\/synchronization\/jobs\/[0-9a-fA-F-]+\/(entities|relationships)/.test( | ||
| config.url, | ||
| ) | ||
| ) { | ||
| if (config.headers) { | ||
| config.headers['Content-Encoding'] = 'gzip'; | ||
| } else { | ||
| config.headers = { | ||
| // Note: Compression is handled differently in RequestClient | ||
| // The data compression would need to be applied at the request level | ||
| // For now, we mark the headers - actual compression may need additional handling | ||
| return { | ||
| ...config, | ||
| headers: { | ||
| ...config.headers, | ||
| 'Content-Encoding': 'gzip', | ||
| }; | ||
| } | ||
| config.data = await gzipData(config.data); | ||
| }, | ||
| }; | ||
| } | ||
| return config; | ||
| }; |
There was a problem hiding this comment.
The compressRequest interceptor sets the 'Content-Encoding: gzip' header but doesn't actually compress the data. The original implementation called gzipData(config.data) to compress the request body. Without actual compression, servers expecting gzipped data will fail to process the request.
| accessToken, | ||
| retryOptions, | ||
| compressUploads, | ||
| alphaOptions, | ||
| proxyUrl, | ||
| }: CreateApiClientInput): ApiClient { |
There was a problem hiding this comment.
The deprecated parameters alphaOptions and proxyUrl are destructured but never used in the function body. Either remove them from the destructuring or explicitly acknowledge their deprecation with a warning log.
| code: 'UNEXPECTED_SYNCRONIZATION_ERROR', | ||
| message: errorMessage, | ||
| cause: err, | ||
| cause: err instanceof Error ? err : undefined, |
There was a problem hiding this comment.
When err is not an Error instance, setting cause to undefined loses error context. Consider converting unknown errors to Error instances or using the original value to preserve debugging information.
| cause: err instanceof Error ? err : undefined, | |
| cause: err, |
|
/canary-release |
There was a problem hiding this comment.
Pull request overview
Copilot reviewed 9 out of 10 changed files in this pull request and generated 1 comment.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
| }, | ||
| ); | ||
| rawBody: compressedData, | ||
| } as any); |
There was a problem hiding this comment.
Using as any type assertion bypasses type safety. Consider defining a proper type for the options parameter that includes the rawBody property, or add a TODO comment explaining this is temporary until the upstream types are updated.
There was a problem hiding this comment.
Already addressed — a `RequestConfigWithRawBody` interface extending `RequestClientRequestConfig` was added (lines 44-47) and is used instead of `as any`. The TODO comment documents that this can be removed once `platform-sdk-fetch` officially exports `rawBody` in its types.
|
🚀 Canary release workflow has been triggered. You can follow the progress here. |
|
❌ Canary release failed. Check the workflow run for details. |
|
/canary-release |
|
🚀 Canary release workflow has been triggered. You can follow the progress here. |
|
❌ Canary release failed. Check the workflow run for details. |
|
/canary-release |
|
🚀 Canary release workflow has been triggered. You can follow the progress here. |
There was a problem hiding this comment.
Pull request overview
Copilot reviewed 9 out of 10 changed files in this pull request and generated 2 comments.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
| client.interceptors.response.use( | ||
| (response) => response, | ||
| (error: any) => { | ||
| async (error: any) => { |
There was a problem hiding this comment.
The error parameter is typed as any, which reduces type safety. Consider defining a proper error type that captures the expected error structure from RequestClient.
|
|
||
| export function synchronizationApiError( | ||
| err: AxiosError<SynchronizationApiErrorResponse>, | ||
| err: RequestClientError | Error | unknown, |
There was a problem hiding this comment.
The parameter accepts unknown in addition to specific error types, but then performs type assertions without proper type guards. Consider adding a type guard function to safely narrow the type before accessing properties.
|
❌ Canary release failed. Check the workflow run for details. |
|
/canary-release |
There was a problem hiding this comment.
Pull request overview
Copilot reviewed 28 out of 29 changed files in this pull request and generated 2 comments.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
| // Store compression flag on client for use by upload functions | ||
| // Default to true to match previous Alpha behavior where uploads were always compressed |
There was a problem hiding this comment.
The default compression behavior (enabled when compressUploads !== false) should be documented. Consider adding a JSDoc comment explaining that compression is enabled by default to maintain backward compatibility with the previous Alpha implementation.
| // Store compression flag on client for use by upload functions | |
| // Default to true to match previous Alpha behavior where uploads were always compressed | |
| /** | |
| * Store compression flag on client for use by upload functions. | |
| * | |
| * Note: Upload compression is enabled by default when `compressUploads !== false` | |
| * to maintain backward compatibility with the previous Alpha implementation, | |
| * where uploads were always compressed. | |
| */ |
| rawBody: compressedData, | ||
| } as RequestConfigWithRawBody); |
There was a problem hiding this comment.
The TODO comment at line 43 indicates this is a temporary workaround. Consider tracking this technical debt more formally (e.g., in a Jira ticket) or removing the TODO if this approach is now the permanent solution.
- Remove skipLibCheck from tsconfig.base.json (revert to match main) - Add skipLibCheck to dist tsconfigs only (needed for platform-sdk-fetch type declarations that reference unresolvable modules) - Replace logger as Function casts with .apply() pattern to avoid TS2556 spread-into-overloaded-function errors - Replace logger.ts double assertion with @ts-expect-error for @types/bunyan RingBuffer.end() incompatibility - Create shared MockApiClient factory in integration-sdk-testing - Update bulkDownloadToJson.test.ts to use shared mock factory - Add integration-sdk-testing as devDependency to cli and runtime
Replace as any casts with @ts-expect-error directives and proper types: - cli-import/cli-export tests: @ts-expect-error for mock ApiClient - api/index.test: @ts-expect-error for deprecated option tests - synchronization/index.test: mockResolvedValueOnce/mockRejectedValueOnce instead of (): any, @ts-expect-error for noop mock - request.ts and managedQuestionFileValidator.test: new Headers() and {} instead of {} as any for mock response fields
Type the error parameter as unknown and narrow via an interface, matching the pattern used in the adjacent error.ts file.
There was a problem hiding this comment.
Pull request overview
Copilot reviewed 32 out of 33 changed files in this pull request and generated 3 comments.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
| baseUrl: 'https://api.us.jupiterone.io', | ||
| onSyncJobCreateResponse(req, res) { | ||
| expect(req.headers['Authorization']).toEqual('Bearer testing-key'); | ||
| // node-fetch used by platform-sdk-fetch stores headers as arrays |
There was a problem hiding this comment.
The comment explains the workaround for array-based headers but doesn't clarify why the change was necessary. Consider adding context about the difference between the previous axios implementation and the new platform-sdk-fetch implementation.
| // node-fetch used by platform-sdk-fetch stores headers as arrays | |
| // platform-sdk-fetch (via node-fetch) represents request headers as arrays, | |
| // whereas the previous axios-based HTTP client exposed them as simple strings. | |
| // Normalize the Authorization header so this test continues to work across both. |
| "lerna": "^7.1.4", | ||
| "lint-staged": "^10.2.6", | ||
| "prettier": "^3.0.0", | ||
| "prettier": "3.2.5", |
There was a problem hiding this comment.
Prettier was pinned to a specific version without explanation. Since the PR is about replacing alpha with platform-sdk-fetch, this change should be explained or moved to a separate commit/PR.
| "prettier": "3.2.5", | |
| "prettier": "^3.2.5", |
package.json
Outdated
| "@types/node": "^18" | ||
| }, | ||
| "overrides": { | ||
| "@sinclair/typebox@^0.32": "0.32.30" |
There was a problem hiding this comment.
The typebox override was added without explanation. Document why this specific version override is necessary to prevent confusion during future dependency updates.
| "@sinclair/typebox@^0.32": "0.32.30" | |
| "@sinclair/typebox@^0.32": "0.32.30" | |
| }, | |
| "overridesComment": { | |
| "@sinclair/typebox@^0.32": "Pin typebox 0.32.x to 0.32.30 to avoid breaking changes in later 0.32 releases that altered validation/runtime behavior; update or remove this override once all dependent packages have been verified against a newer compatible version." |
CI uses tsc -b with tsconfig.json (not tsconfig.dist.json). Add skipLibCheck to packages that depend on platform-sdk-fetch, and fix Headers type mismatch in test mock helpers.
- Replace custom ErrorWithRequestConfig interface with proper isRequestClientError type guard from platform-sdk-fetch - Remove dead config.data deletion (RequestClientError.config does not have a data property) - Fix test: use RequestClientError instead of plain Error with Object.assign, fix "Authroization" typo, verify non-sensitive headers are preserved
There was a problem hiding this comment.
Pull request overview
Copilot reviewed 37 out of 38 changed files in this pull request and generated 1 comment.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
| interface RequestConfigWithRawBody extends RequestClientRequestConfig { | ||
| rawBody?: Buffer; | ||
| } |
There was a problem hiding this comment.
The TODO comment indicates this interface should be removed once platform-sdk-fetch officially exports rawBody. Consider creating a tracking issue or adding a reference to ensure this technical debt is addressed when the dependency is updated.
|
/canary-release |
|
🚀 Canary release workflow has been triggered. You can follow the progress here. |
|
✅ Canary release published successfully! Published packages:
Install with: npm install @jupiterone/cli@17.2.2-canary-1188-21651197416.0
npm install @jupiterone/integration-sdk-cli@17.2.2-canary-1188-21651197416.0
npm install @jupiterone/integration-sdk-core@17.2.2-canary-1188-21651197416.0
npm install @jupiterone/integration-sdk-dev-tools@17.2.2-canary-1188-21651197416.0
npm install @jupiterone/integration-sdk-entities@17.2.2-canary-1188-21651197416.0
npm install @jupiterone/integration-sdk-entity-validator@17.2.2-canary-1188-21651197416.0
npm install @jupiterone/integration-sdk-http-client@17.2.2-canary-1188-21651197416.0
npm install @jupiterone/integration-sdk-runtime@17.2.2-canary-1188-21651197416.0
npm install @jupiterone/integration-sdk-testing@17.2.2-canary-1188-21651197416.0 |
Downstream consumers (e.g. graph-aws) still pass alphaOptions to createApiClient. Throwing breaks them at runtime. Switch to console.warn deprecation notices so migration can proceed incrementally.
|
/canary-release |
|
🚀 Canary release workflow has been triggered. You can follow the progress here. |
|
✅ Canary release published successfully! Published packages:
Install with: npm install @jupiterone/cli@17.2.2-canary-1188-21651857611.0
npm install @jupiterone/integration-sdk-cli@17.2.2-canary-1188-21651857611.0
npm install @jupiterone/integration-sdk-core@17.2.2-canary-1188-21651857611.0
npm install @jupiterone/integration-sdk-dev-tools@17.2.2-canary-1188-21651857611.0
npm install @jupiterone/integration-sdk-entities@17.2.2-canary-1188-21651857611.0
npm install @jupiterone/integration-sdk-entity-validator@17.2.2-canary-1188-21651857611.0
npm install @jupiterone/integration-sdk-http-client@17.2.2-canary-1188-21651857611.0
npm install @jupiterone/integration-sdk-runtime@17.2.2-canary-1188-21651857611.0
npm install @jupiterone/integration-sdk-testing@17.2.2-canary-1188-21651857611.0 |
ESLint no-console rule blocks console.warn in CI. Switch to process.emitWarning with DeprecationWarning type, which is the Node.js standard for deprecation notices.
There was a problem hiding this comment.
Pull request overview
Copilot reviewed 37 out of 38 changed files in this pull request and generated 2 comments.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
| if: steps.changed.outputs.has_changes == 'true' | ||
| run: | | ||
| PRERELEASE_ID="canary-${{ github.event.issue.number }}-${{ github.run_attempt }}" | ||
| PRERELEASE_ID="canary-${{ github.event.issue.number }}-${{ github.run_id }}" |
There was a problem hiding this comment.
Changed from github.run_attempt to github.run_id for generating the prerelease ID. This changes the versioning scheme for canary releases. Verify that downstream consumers can handle this versioning change, and ensure that canary version uniqueness is maintained across workflow runs.
| * Internal flag indicating whether uploads should be compressed. | ||
| * @internal | ||
| */ | ||
| _compressUploads?: boolean; |
There was a problem hiding this comment.
The _compressUploads flag is stored as a mutable property on the client object. Consider making this configuration immutable by storing it in a WeakMap or closure to prevent accidental modification at runtime.
| _compressUploads?: boolean; | |
| readonly _compressUploads?: boolean; |
|
/canary-release |
|
🚀 Canary release workflow has been triggered. You can follow the progress here. |
|
✅ Canary release published successfully! Published packages:
Install with: npm install @jupiterone/cli@17.2.2-canary-1188-21682081974.0
npm install @jupiterone/integration-sdk-cli@17.2.2-canary-1188-21682081974.0
npm install @jupiterone/integration-sdk-core@17.2.2-canary-1188-21682081974.0
npm install @jupiterone/integration-sdk-dev-tools@17.2.2-canary-1188-21682081974.0
npm install @jupiterone/integration-sdk-entities@17.2.2-canary-1188-21682081974.0
npm install @jupiterone/integration-sdk-entity-validator@17.2.2-canary-1188-21682081974.0
npm install @jupiterone/integration-sdk-http-client@17.2.2-canary-1188-21682081974.0
npm install @jupiterone/integration-sdk-runtime@17.2.2-canary-1188-21682081974.0
npm install @jupiterone/integration-sdk-testing@17.2.2-canary-1188-21682081974.0 |
Add npm override to force fast-xml-parser@5.3.4, fixing the RangeError DoS vulnerability in numeric entities parsing.
There was a problem hiding this comment.
Pull request overview
Copilot reviewed 37 out of 38 changed files in this pull request and generated 3 comments.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
| * Extended request config that includes rawBody for sending pre-serialized/compressed data. | ||
| * This extends the standard RequestClientRequestConfig to support gzip-compressed uploads. | ||
| * | ||
| * TODO: Remove this interface once platform-sdk-fetch officially exports rawBody in its types. |
There was a problem hiding this comment.
This TODO comment should include a link to the tracking issue or PR in the platform-sdk-fetch repository where rawBody type support is being discussed or implemented. This will make it easier to track when this workaround can be removed.
| * TODO: Remove this interface once platform-sdk-fetch officially exports rawBody in its types. | |
| * TODO: Remove this interface once platform-sdk-fetch officially exports rawBody in its types. | |
| * Tracking issue/PR: https://github.com/jupiterone/platform-sdk-fetch/issues?q=rawBody |
| } | ||
|
|
||
| function isRequestUploadTooLargeError(err): boolean { | ||
| function isRequestUploadTooLargeError(err: Record<string, any>): boolean { |
There was a problem hiding this comment.
The parameter type Record<string, any> is too permissive. Consider creating a specific type or using unknown with proper type guards to ensure type safety. This would make the function more robust and easier to maintain.
| function cleanRequestError(err: unknown) { | ||
| if (isRequestClientError(err) && err.config?.headers?.Authorization) { | ||
| delete err.config.headers.Authorization; | ||
| } | ||
|
|
||
| if (err.config?.data) { | ||
| delete err.config.data; | ||
| } | ||
| } |
There was a problem hiding this comment.
The removed data cleanup (delete err.config.data) is intentional, but the reason is not documented. Consider adding a comment explaining why data is no longer cleaned from errors in the RequestClient implementation, or confirming this is the intended behavior.
Add package.json exports map for @jupiterone/integration-sdk-testing
with a separate ./mockApiClient entry point. This allows CLI tests
to import createMockApiClient without loading recording.ts, which
uses polly/graceful-fs and conflicts with jest.mock('fs').
Addresses review feedback from @ryanmcafee.
3 participants
Summary
Replace
@lifeomic/alphawith@jupiterone/platform-sdk-fetchcanary release (6.0.3-canary-487-1.0).Changes
packages/integration-sdk-runtime/package.jsonpackages/integration-sdk-runtime/src/api/index.tspackages/integration-sdk-runtime/src/synchronization/*.tspackages/cli/src/import/importAssetsFromCsv.tstsconfig.dist.jsonBreaking Changes
ApiClienttype is nowRequestClientinstead ofAlphaalphaOptionsandproxyUrl(not supported by RequestClient)Test Plan
Related