---
name: bijection-bright-data-sholajegede
description: "Evaluate and integrate the Bright Data Sholajegede component with Bijection."
---

# Bright Data Sholajegede

Cache Bright Data SERP and Web Unlocker results in Bijection with configurable TTLs and reactive queries.

- Package: @bijectionhq/bright-data-sholajegede
- Category: Integrations
- Status: Reference
- License: Apache-2.0
- Bijection source (repository access required): https://github.com/bijectionhq/bright-data-sholajegede/tree/56e3626498bb4a680b42bc615477bbe4575947e7
- Upstream: https://github.com/sholajegede/convex-bright-data/tree/2505cfcbf69d6c3c58658d05851e19490da3e159
- Documentation: https://docs.bijection.com/components/using
- Directory: https://bijection.com/components/bright-data-sholajegede

## Get the source

Bijection repository access is required. Request access at https://bijection.com/contact.

```sh
git clone https://github.com/bijectionhq/bright-data-sholajegede.git
cd bright-data-sholajegede
git checkout 56e3626498bb4a680b42bc615477bbe4575947e7
```

## Before using this component

Read the package README at the recorded revision for setup, dependencies, and API examples. Upstream documentation describes the original package and may differ from the Bijection adaptation. This is a source candidate for evaluation. Catalog inclusion does not establish npm availability or runtime qualification. Check compatibility with your SDK and deployment before adoption. External providers run their own compute.

## Integration workflow

1. Read the source README and package manifest at the recorded revision.
2. Confirm the required SDK, dependency availability, and runtime compatibility.
3. Follow the component's documented setup and configuration. Never invent an npm install command from a catalog package name.
4. Keep credentials in the project's existing secret store.
5. Follow the project's execution rules for verification and report what was actually checked.

## Original upstream skill

The following guidance describes @sholajegede/convex-bright-data. Its installation commands and APIs refer to the upstream package. Evaluate compatibility with the Bijection source separately.


# Bright Data

## Instructions

Use Bright Data to cache bright data serp api and web unlocker results in convex tables with configurable ttls and reactive queries to reduce api costs. This Convex component integrates directly with your backend.

### Installation

```bash
npm install @sholajegede/convex-bright-data
```

### Capabilities

- Eliminate redundant Bright Data API calls with configurable TTL-based caching
- Get real-time updates on cached search results and scraped content via reactive queries
- Save development time with drop-in component that handles caching boilerplate
- Reduce external API costs by serving fresh data from Convex tables

## Examples

### how to cache web scraping results in Convex

The Bright Data component automatically caches scraped page content in Convex tables with configurable TTLs. Call the scrape action once to fetch and store data, then use reactive queries to access cached content without re-fetching until the TTL expires.

### reactive SERP API caching with Convex

This component wraps Bright Data's SERP API with Convex-native caching. Search results are stored in component-owned tables and accessed via useQuery for live updates. No polling required - Convex automatically pushes updates when cache refreshes.

### reduce Bright Data API costs with caching

The component prevents redundant API calls by checking cache freshness before hitting Bright Data APIs. Cached results are served instantly if still within TTL, and you can invalidate entries on-demand to force fresh fetches when needed.

## When NOT to use

- When a simpler built-in solution exists for your specific use case
- If you are not using Convex as your backend
- When the functionality provided by Bright Data is not needed

## Troubleshooting

**How does the Bright Data Convex component handle cache TTLs?**

The @sholajegede/convex-bright-data component supports configurable TTLs per request or global defaults (1 hour for searches, 6 hours for pages). Cached data includes fetchedAt and expiresAt timestamps, with an isFresh boolean indicating if data is still within TTL.

**Can I force refresh cached Bright Data results?**

Yes, the Bright Data component provides an invalidate method that deletes cached entries for specific queries or URLs. This forces a fresh fetch from Bright Data APIs on the next request while preserving the reactive caching pattern.

**What Bright Data services does this Convex component support?**

The @sholajegede/convex-bright-data component supports Bright Data's SERP API for Google search results (web, news, shopping, images, videos) and Web Unlocker for page scraping. Both services are wrapped with the same TTL-based caching and reactive query pattern.

**How do reactive queries work with cached Bright Data results?**

The component stores Bright Data results in Convex tables. Call the action once to fetch and cache data, then use useQuery on the cached results. Convex automatically notifies all subscribers when cache updates, eliminating the need for polling or manual refresh logic.

## Resources

- [npm package](https://www.npmjs.com/package/%40sholajegede%2Fconvex-bright-data)
- [GitHub repository](https://github.com/sholajegede/convex-bright-data)
- [Live demo](https://convex-brightdata-demo.vercel.app)
- [Convex Components Directory](https://www.convex.dev/components/sholajegede/convex-bright-data)
- [Convex documentation](https://docs.convex.dev)