-
Notifications
You must be signed in to change notification settings - Fork 5.5k
Firecrawl - search action #17013
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Firecrawl - search action #17013
Conversation
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎ 3 Skipped Deployments
|
|
""" WalkthroughA new "firecrawl-search" action was introduced, enabling web searches with content extraction via the Firecrawl API. Supporting methods and configuration options were added, including a new Changes
Sequence Diagram(s)sequenceDiagram
participant User
participant FirecrawlSearchAction
participant FirecrawlApp
participant FirecrawlAPI
User->>FirecrawlSearchAction: Provide search query and options
FirecrawlSearchAction->>FirecrawlApp: Call search(opts)
FirecrawlApp->>FirecrawlAPI: POST /search with opts
FirecrawlAPI-->>FirecrawlApp: Return search results
FirecrawlApp-->>FirecrawlSearchAction: Return search results
FirecrawlSearchAction-->>User: Return summary and results
Assessment against linked issues
Assessment against linked issues: Out-of-scope changes
Poem
Warning There were issues while running some tools. Please review the errors and either fix the tool's configuration or disable the tool if it's a critical failure. 🔧 ESLint
components/firecrawl/actions/search/search.mjsOops! Something went wrong! :( ESLint: 8.57.1 Error [ERR_MODULE_NOT_FOUND]: Cannot find package 'jsonc-eslint-parser' imported from /eslint.config.mjs 📜 Recent review detailsConfiguration used: CodeRabbit UI 📒 Files selected for processing (1)
✅ Files skipped from review due to trivial changes (1)
⏰ Context from checks skipped due to timeout of 90000ms (3)
✨ Finishing Touches
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
SupportNeed help? Create a ticket on our support page for assistance with any issues or questions. Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (Invoked using PR comments)
Other keywords and placeholders
CodeRabbit Configuration File (
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Actionable comments posted: 1
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
⛔ Files ignored due to path filters (1)
pnpm-lock.yamlis excluded by!**/pnpm-lock.yaml
📒 Files selected for processing (8)
components/firecrawl/actions/crawl-url/crawl-url.mjs(1 hunks)components/firecrawl/actions/extract-data/extract-data.mjs(1 hunks)components/firecrawl/actions/get-crawl-status/get-crawl-status.mjs(1 hunks)components/firecrawl/actions/get-extract-status/get-extract-status.mjs(1 hunks)components/firecrawl/actions/scrape-page/scrape-page.mjs(1 hunks)components/firecrawl/actions/search/search.mjs(1 hunks)components/firecrawl/firecrawl.app.mjs(1 hunks)components/firecrawl/package.json(2 hunks)
⏰ Context from checks skipped due to timeout of 90000ms (4)
- GitHub Check: Verify TypeScript components
- GitHub Check: pnpm publish
- GitHub Check: Publish TypeScript components
- GitHub Check: Lint Code Base
🔇 Additional comments (10)
components/firecrawl/firecrawl.app.mjs (1)
80-86: LGTM! The search method implementation follows established patterns.The new
searchmethod is consistent with other API methods in this module, using the same parameter structure and request pattern. The POST method and/searchendpoint are appropriate for search operations.components/firecrawl/actions/extract-data/extract-data.mjs (1)
9-9: Version bump looks appropriate.The patch version increment aligns with the coordinated release that includes the new search functionality.
components/firecrawl/actions/crawl-url/crawl-url.mjs (1)
8-8: Version bump is consistent with the coordinated release.The patch version increment from 1.0.2 to 1.0.3 aligns with the package-wide updates for the new search functionality.
components/firecrawl/package.json (2)
3-3: Appropriate minor version bump for new functionality.The version increment from 1.1.0 to 1.2.0 correctly reflects the addition of new search functionality using semantic versioning.
16-16:✅ Verification successful
Verify the necessity and compatibility of the platform dependency update.
The dependency update from
^3.0.0to^3.1.0should be verified to ensure it's required for the new search functionality and doesn't introduce any breaking changes.
🏁 Script executed:
#!/bin/bash # Description: Check if the new search action uses any features from @pipedream/platform ^3.1.0 # Expected: Find usage patterns that require the newer version # Search for any usage of @pipedream/platform imports or features in the search action fd -e mjs -e js . -x rg -l "@pipedream/platform" {} \; # Look for any new platform features that might require ^3.1.0 rg -A 5 -B 5 "platform|Platform" components/firecrawl/Length of output: 65760
🏁 Script executed:
#!/bin/bash # List all files under components/firecrawl to identify code files fd -t f components/firecrawlLength of output: 416
🏁 Script executed:
#!/bin/bash # Recursively list all files in the firecrawl component directory find components/firecrawl -type fLength of output: 542
No v3.1.0-only features detected; bump is safe
We scanned every file under components/firecrawl and found no imports from
@pipedream/platform—the new search action uses only native APIs and shared constants/utils. Since 3.1.0 is a minor, backward-compatible release, you can proceed with this dependency update without further changes.components/firecrawl/actions/get-crawl-status/get-crawl-status.mjs (1)
7-7: Version update looks good.The version increment from
0.0.3to0.0.4aligns with the coordinated release across Firecrawl actions.components/firecrawl/actions/get-extract-status/get-extract-status.mjs (1)
7-7: Version update looks good.The version increment from
0.0.1to0.0.2aligns with the coordinated release across Firecrawl actions.components/firecrawl/actions/scrape-page/scrape-page.mjs (1)
10-10: Version update looks good.The version increment from
1.0.1to1.0.2aligns with the coordinated release across Firecrawl actions.components/firecrawl/actions/search/search.mjs (2)
1-15: Well-structured action setup.The import, export structure, and basic configuration follow established patterns. The query prop is appropriately marked as required.
16-93: Comprehensive and well-organized prop definitions.The scrape format options are thorough, time-based search filters use standard syntax, and the props have good defaults and descriptions. The optional nature of most props provides good flexibility.
GTFalcao
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM!
Resolves #16951
Summary by CodeRabbit
New Features
Chores