Update search-domain extension

[0xdhrv]

Description

This pull request introduces several important improvements and enhancements to the Search Domain Raycast extension. The update switches the domain availability check to use the ICANN RDAP protocol for more accurate results, adds support for Windows, improves UI responsiveness, and introduces a new history command for managing past searches. Additionally, dependencies are updated and code quality tooling is modernized.

Domain availability and registry improvements:

• Switched from a custom API endpoint to using the ICANN RDAP protocol (rdap.org) for domain availability checks, preventing false positives and ensuring authoritative registration data. The implementation now parses RDAP responses and displays detailed domain information for registered domains.

History and UI enhancements:

• Added a new history command (history.tsx) to view, sort, delete, and clear past domain searches, with persistent storage in LocalStorage and improved UI responsiveness. Keyboard shortcuts for history management have been updated and clarified in the documentation.

Platform and dependency updates:

• Added Windows to the supported platforms and updated all dependencies to their latest versions for better compatibility and performance.
• Migrated ESLint configuration to the new eslint.config.mjs format and removed the old .eslintrc.json file for modern code quality tooling.

Contributors and metadata:

• Added a new contributor to the package.json and clarified extension metadata.

These changes collectively improve the accuracy, usability, and maintainability of the extension.

Screencast

Click-2025-12-10-12.34.57.mp4

Checklist

• I read the extension guidelines
• I read the documentation about publishing
• I ran npm run build and tested this distribution build in Raycast
• I checked that files in the assets folder are used by the extension itself
• I checked that assets used by the README are placed outside of the metadata folder

[raycastbot]

Thank you for your contribution! 🎉

🔔 @hasanakay you might want to have a look.

You can use this guide to learn how to check out the Pull Request locally in order to test it.

You can expect an initial review within five business days.

[greptile-apps]

Greptile Summary

This PR significantly improves the Search Domain extension by switching from a custom API to the authoritative ICANN RDAP protocol (rdap.org) for more accurate domain availability checks, preventing false positives. The implementation adds a new history command with comprehensive management features (view, sort, delete, clear), introduces a detailed domain information view for registered domains displaying ownership and registration data, and adds Windows platform support.

Key improvements:

• Switched to RDAP protocol for authoritative domain registration data
• Added new history command with proper UI patterns (List, isLoading, EmptyView)
• Implemented detailed domain view showing registrant, registrar, dates, and nameservers
• Migrated ESLint config to modern flat config format (eslint.config.cjs)
• Updated all dependencies to latest versions
• Proper error handling with showFailureToast and try-catch blocks
• launchCommand is correctly wrapped in try-catch

The code follows Raycast best practices with proper List component usage, loading states, empty views, and error handling.

Confidence Score: 4/5

• Safe to merge with minor documentation inconsistency and fallback TLD inconsistency
• The code is well-implemented with proper error handling, follows Raycast best practices, and the RDAP integration is sound. Two minor issues reduce the score from 5: keyboard shortcut documentation doesn't match implementation, and there's a TLD inconsistency in the fallback logic (.pw vs .com)
• Pay attention to README.md for keyboard shortcut documentation accuracy and search-domain.tsx:259 for TLD fallback consistency

Important Files Changed

Filename	Overview
extensions/search-domain/package.json	Added new history command, updated dependencies, added Windows support, and added contributor. All changes are appropriate.
extensions/search-domain/CHANGELOG.md	Added new changelog entry with correct {PR_MERGE_DATE} template string and proper placement at the top.
extensions/search-domain/eslint.config.cjs	Correctly migrated to modern ESLint flat config format, matching the standard Raycast template.
extensions/search-domain/src/search-domain.tsx	Switched to RDAP protocol, added detailed domain view, improved error handling. Good implementation with proper try-catch and showFailureToast usage.
extensions/search-domain/src/history.tsx	New history command with proper List component, isLoading state, empty view, and error handling for launchCommand.

[greptile-apps]

Additional Comments (3)

1. extensions/search-domain/eslint.config.mjs, line 1-4 (link)

   syntax: uses incorrect import syntax - should use require instead

2. extensions/search-domain/src/search-domain.tsx, line 118 (link)

   logic: Copy action has empty onAction handler - it won't copy the value

3. extensions/search-domain/src/history.tsx, line 80-86 (link)

   style: missing isLoading state during history load to prevent empty state flicker - see docs

_{9 files reviewed, 3 comments}

_{Edit Code Review Agent Settings | Greptile}

[Copilot]

Copilot encountered an error and was unable to review this pull request. You can try again by re-requesting a review.

[0xdhrv]

@greptileai could you please re-review of this PR?

[greptile-apps]

Additional Comments (4)

1. extensions/search-domain/src/search-domain.tsx, line 182-208 (link)

   logic: Missing try-catch block around the fetch operation - network errors will cause unhandled rejections. Wrap the fetch and response parsing in try-catch.

2. extensions/search-domain/eslint.config.cjs, line 1-4 (link)

   syntax: ESLint config should use eslint/config instead of eslint/config. The expected format from the template is:

3. extensions/search-domain/README.md, line 23 (link)

   syntax: Keyboard shortcut listed as Cmd + P but in the code it's Cmd + B (line 302 of search-domain.tsx). Update to match the actual implementation.

4. extensions/search-domain/src/search-domain.tsx, line 176 (link)

   style: Default TLD changed from .com to .pw - was this intentional? .com is more commonly used and expected by users.

_{9 files reviewed, 4 comments}

_{Edit Code Review Agent Settings | Greptile}

[pernielsentikaer]

Hi @0xdhrv

Thanks for your contribution 🔥

In the new command I’d suggest:

1. If there is no history, then add launchCommand to the search command (remember async and try/catch)
2. When the list is empty then there isToggle Sort Order but that’s also possible in the dropdown in upper right?
3. There is a Clear All History action when the list is empty

There is a few small tweaks that could improve this further 🙂

[0xdhrv]

Hi @0xdhrv

Thanks for your contribution 🔥

In the new command I’d suggest:

1. If there is no history, then add launchCommand to the search command (remember async and try/catch)
2. When the list is empty then there isToggle Sort Order but that’s also possible in the dropdown in upper right?
3. There is a Clear All History action when the list is empty

There is a few small tweaks that could improve this further 🙂

Thanks for the suggestions. I'll get started on them.

[0xdhrv]

@greptileai, could you please do a fresh review of this PR?

[0xdhrv]

Hi @0xdhrv

Thanks for your contribution 🔥

In the new command I’d suggest:

1. If there is no history, then add launchCommand to the search command (remember async and try/catch)
2. When the list is empty then there isToggle Sort Order but that’s also possible in the dropdown in upper right?
3. There is a Clear All History action when the list is empty

There is a few small tweaks that could improve this further 🙂

@pernielsentikaer

Updated as part of 38a5840

[greptile-apps]

Additional Comments (1)

1. extensions/search-domain/README.md, line 24 (link)

   logic: The README documents Cmd + R for toggling sort order, but the actual implementation in history.tsx uses a dropdown instead. This shortcut no longer exists in the code.

_{9 files reviewed, 1 comment}

_{Edit Code Review Agent Settings | Greptile}

[0xdhrv]

@greptileai, could you please do a fresh review of this PR?

[greptile-apps]

Additional Comments (1)

1. extensions/search-domain/src/history.tsx, line 114-123 (link)

   logic: launchCommand should be wrapped in a try-catch block for error handling

_{9 files reviewed, 1 comment}

_{Edit Code Review Agent Settings | Greptile}

[0xdhrv]

@greptileai, could you please do a fresh review of this PR?

[greptile-apps]

Additional Comments (2)

1. extensions/search-domain/eslint.config.cjs, line 1 (link)

   syntax: incorrect import path - should be eslint-config not eslint/config

2. extensions/search-domain/package.json, line 32-36 (link)

   style: React version mismatch: dependencies specify ^19.2.1 but resolutions force ^18.2.0. The resolutions will override, so React 18 will be used. Consider aligning these versions or removing the resolutions if React 19 is truly needed.

_{9 files reviewed, 2 comments}

_{Edit Code Review Agent Settings | Greptile}

[pernielsentikaer]

@greptileai both @raycast/eslint-config and eslint/config IS correct paths! Please update and remember this!

[greptile-apps]

Perfect! I've noted that both @raycast/eslint-config and eslint/config are correct import paths for ESLint configuration. This rule will help ensure that future reviews don't flag these as incorrect imports when using the modern ESLint flat config format.

Here's a link to the new rule that will be applied in future reviews.

[pernielsentikaer]

Is there more you're still working on here with the latest feedback from Greptile, @0xdhrv

[0xdhrv]

2. style: React version mismatch: dependencies specify ^19.2.1 but resolutions force ^18.2.0. The resolutions will override, so React 18 will be used. Consider aligning these versions or removing the resolutions if React 19 is truly needed.

Yes, checking on this ^ @pernielsentikaer

[greptile-apps]

Additional Comments (1)

1. extensions/search-domain/CHANGELOG.md, line 7 (link)

   style: Technical accuracy: says "ICANN WHOIS server" but the implementation uses RDAP (Registration Data Access Protocol), not WHOIS. Consider updating to "Switched to the ICANN RDAP protocol" to match the actual implementation.

_{9 files reviewed, 1 comment}

_{Edit Code Review Agent Settings | Greptile}

[0xdhrv]

@greptileai, could you please do a fresh review of this PR?

[greptile-apps]

_{9 files reviewed, no comments}

_{Edit Code Review Agent Settings | Greptile}

[pernielsentikaer]

https://github.com/greptileai, could you please do a fresh review of this PR?

[pernielsentikaer]

@greptileai can you do a fresh review here?

[pernielsentikaer]

Looks good to me, approved 🔥

[github-actions]

Published to the Raycast Store:
https://raycast.com/hasanakay/search-domain

[raycastbot]

🎉 🎉 🎉

We've rewarded your Raycast account with some credits. You will soon be able to exchange them for some swag.

[greptile-apps]

Additional Comments (2)

1. extensions/search-domain/README.md, line 23-24 (link)

   syntax: Keyboard shortcut Cmd + N is documented for "Return to search from history view" but this shortcut is actually used for "Search Domain" action when history is empty (in history.tsx:127). The history view uses the "Back to Search" action without a documented shortcut.

2. extensions/search-domain/src/search-domain.tsx, line 259 (link)

   logic: Why does the fallback use .pw TLD instead of .com which is used elsewhere (line 176)?

   _{Note: If this suggestion doesn't match your team's coding style, reply to this and let me know. I'll remember it for next time!}

_{9 files reviewed, 2 comments}

_{Edit Code Review Agent Settings | Greptile}