Upgrade quant-client to v4.12.0, fix env logs, and extend tests#8
Merged
Conversation
- Upgrade @quantcdn/quant-client from 4.3.0 to 4.12.0 - Fix env logs returning no data (response uses logEvents, not logs) - Simplify API client config to use Configuration.accessToken - Use machine_name consistently for project/crawler selection - Add autocomplete prompts for crawler project/crawler selection - Add DOM lib to tsconfig for VRT type annotations - Expand explicit params for backup and metrics API calls - Replace ASCII banner with cleaner logo in cyan - Extend API client test suite from 14 to 52 tests with mocked SDK
steveworley
approved these changes
Mar 9, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
@quantcdn/quant-clientfrom 4.3.0 to 4.12.0 (no breaking changes for current CLI usage;crawlersListvoid return type reported upstream)qc env logs— was returning no data because the API response useslogEventskey, notlogsConfiguration.accessTokenmachine_nameusage — project and crawler selection now always usesmachine_namefor API calls instead of falling back to displaynameTest plan
qc env logsreturns log dataqc crawler runautocomplete promptsqc project selectwith machine_name