@haatlabs-core/provider-amazon

中文文档
0.18.5发布于 2026/11/14Apache-2.0TypeScriptESM + CJS近 30 天下载 5124

Amazon search, products and suggestions as a ProductSource.

原始使用文档
文档目录8 节
  1. Install
  2. What it does
  3. Options
  4. Errors
  5. Gateway and deadlines
  6. Fixtures
  7. Testing
  8. Hosted services

@haatlabs-core/provider-amazon

@haatlabs-core/provider-amazon/contracts (0.12.1): the error codes (PROVIDER_AMAZON_ERRORS), the sources' schemas and types (ProductRefSchema, SourceInfoSchema, ProductSource...), the marketplaces and the link and text helpers: everything but createAmazonSource, with nothing of Node. A project's contracts, which its pages load, import from here and never the root, which is for Node.

Install

pnpm add @haatlabs-core/provider-amazon

It leaves one package to your app, so the app holds one copy: zod.

What it does

Amazon search, products and suggestions through an Amazon scraper, called directly or through a services gateway: createAmazonSource(options) gives a ProductSource (search, product, autocomplete, parseLink, health). It caches nothing: wrap a call in cachedCall (@haatlabs-core/providers) for AMAZON_CACHE_SECONDS (search and product an hour, suggestions a day). AMAZON_IMAGE_HOSTS are the hosts a content security policy names.

Options

baseUrl (the scraper, the gateway's /amazon, or the hosted API), timeoutMs, apiKey (the hosted API's) or gatewayKey (the gateway's; setting both is a RangeError), proxyEnabled (Japan and Australia need a proxy that exits there), fetch, maxConcurrent (12 calls in flight), maxWaitMs (10 s for a place before the call is refused) and maxResponseBytes (2 MiB).

Errors

SOURCE_BAD_REQUEST (400), SOURCE_PRODUCT_NOT_FOUND (404, for a product only), SOURCE_UNAVAILABLE (503, transient: away, slow, busy, or no place within maxWaitMs) and SOURCE_ERROR (503: an answer that cannot be used). A project spreads PROVIDER_AMAZON_ERRORS into defineErrors. A 429 or 5xx carries retryAfterMs from its Retry-After (seconds or a date, at most five minutes). Called directly, a refusal's body is never read: the connection is let go.

Gateway and deadlines

Each call takes a CallContext (tier, priority, deadlineMs); with gatewayKey it sends the gateway's headers, tier 4 in the background when there is none. The call's time limit is timeoutMs, or deadlineMs when that is sooner (localTimeoutMs), and it starts before the wait for one of the maxConcurrent places: the wait counts, and a call whose time ran out while it waited is never made. The gateway is given what is left of that limit, never longer. The deadline is each call's: a caller's retry starts it again, so a caller that retries gives each try what is left of its own budget. Through the gateway a refusal carries an UpstreamStatusError as its cause: isGatewayRefusal(error) is true for the gateway's 401 and 403 (both SOURCE_UNAVAILABLE), and only the gateway's own bad_request 400 is a contract error.

Fixtures

@haatlabs-core/provider-amazon/fixtures: amazonFixtures.product, .search and .autocomplete, answers recorded from the real scraper.

Testing

@haatlabs-core/provider-amazon/testing: createFakeSource(options), a second ProductSource with one market, for tests that must not assume Amazon. The package's own tests are unit tests on the fixtures: pnpm --filter @haatlabs-core/provider-amazon test.

Hosted services

Without a scraper of your own, read Amazon through the Haatlabs API on RapidAPI: set haatlabsApiKey (your RapidAPI key) and baseUrl: 'https://haatlabs-api.p.rapidapi.com' (apiKey and gatewayKey stay null). Every marketplace is available; there are no suggestions (autocomplete is absent); a refusal keeps its message, and a used-up quota or a refused key is SOURCE_UNAVAILABLE that is not transient. See @haatlabs-core/services and https://haatlabs.shop/docs/services/

版本与发布记录

@haatlabs-core/provider-amazon 共发布 27 个版本,首次发布于 2026/10/23;过去 12 个月发布了 27 个版本。

版本发布日期距今
0.18.5latest2026/11/143 天前
0.18.42026/11/133 天前
0.18.32026/11/134 天前
0.18.22026/11/134 天前
0.18.12026/11/134 天前
0.18.02026/11/134 天前

关于 @haatlabs-core/provider-amazon 的常见问题

@haatlabs-core/provider-amazon 是什么?

Amazon search, products and suggestions as a ProductSource.

如何安装 @haatlabs-core/provider-amazon?

在项目目录运行 npm install @haatlabs-core/provider-amazon,或使用 pnpm add / yarn add / bun add。它还需要宿主项目提供 peer 依赖:zod(^4.6.5)。npm 7 及以上与 pnpm 8 及以上默认会自动安装必需的 peer 依赖,Yarn 需要手动安装。

@haatlabs-core/provider-amazon 支持 TypeScript 吗?

支持。包内自带 TypeScript 类型声明(package.json 声明了 types 入口),安装后即可获得类型提示,无需再安装 @types 包。

@haatlabs-core/provider-amazon 支持 ESM 还是 CommonJS?

同时提供 ES Module 与 CommonJS 入口,import 和 require() 都可以使用,打包工具会自动选择合适的版本。

@haatlabs-core/provider-amazon 需要什么版本的 Node.js?

package.json 的 engines 字段要求 Node.js >=24。版本不符时 npm 默认只给出警告,开启 engine-strict 后会拒绝安装。

@haatlabs-core/provider-amazon 可以商用吗?

@haatlabs-core/provider-amazon 使用 Apache-2.0 许可。宽松许可:允许商业使用、修改和再分发,并附带明确的专利授权;分发时需保留许可与 NOTICE 文件,修改过的文件要注明改动。以上为概括,不构成法律意见,请以许可原文为准。

@haatlabs-core/provider-amazon 的下载量有多少?

根据 npm 官方下载统计,@haatlabs-core/provider-amazon 在 2026/10/17 – 2026/11/15 这 30 天内被下载 5,124 次,日均约 171 次。下载量会把 CI 构建、镜像同步和作为其他包依赖的安装一并计入,适合横向比较热度,不能直接等同于使用人数。

@haatlabs-core/provider-amazon 还在维护吗?

最新版本 0.18.5 发布于 2026/11/14(3 天前);至今共发布 27 个版本,其中过去 12 个月发布了 27 个;首次发布于 2026/10/23。发布频率只是参考信号:功能稳定的工具可能很少需要更新,建议结合源码仓库的 issue 和提交记录判断。