Add catenary-raycast extension

[quacksire]

Description

Adds a Raycast extension that integrates with the Catenary Maps API to surface real-time transit departures for nearby stops or user-searched stops. It includes support for location-based discovery, mode filters, and displaying route metadata (name, headsign, bay, etc.) in the Raycast UI.

Screencast

https://youtu.be/2BLuYItcI78

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]

Congratulations on your new Raycast extension! 🚀

You can expect an initial review within five business days.

Once the PR is approved and merged, the extension will be available on our Store.

[greptile-apps]

Greptile Overview

Greptile Summary

This PR adds a new Raycast extension for Catenary Maps that integrates real-time transit departures. The implementation is well-structured with proper TypeScript types, error handling, and React best practices.

Key Features:

• Location-based discovery using IP geolocation via Cloudflare Worker
• Text search for stops using Catenary's Birch API
• Real-time departure information with filtering by transit mode (bus, rail, metro)
• Recent stops history with LocalStorage
• Proper loading states and empty view handling

Issues Found:

• CHANGELOG.md uses an actual date (2025-11-24) instead of the template string {PR_MERGE_DATE}
• ESLint configuration uses .eslintrc.json format instead of the recommended eslint.config.js format

Positive Aspects:

• Proper metadata folder with screenshots included for this new extension
• Good use of @raycast/utils hooks (useFetch)
• Comprehensive error handling with try-catch blocks
• Loading states properly implemented to avoid empty state flicker
• Command includes subtitle as recommended for single-command extensions
• Strong TypeScript typing throughout
• Clean code structure with well-organized helper functions

Confidence Score: 4/5

• This PR is safe to merge after addressing the CHANGELOG date format issue
• Score reflects well-implemented functionality with proper error handling and React best practices. The two issues found are minor: one is a required fix (CHANGELOG date format) and one is a style recommendation (ESLint config format). The extension demonstrates good code quality with comprehensive TypeScript types, proper use of Raycast APIs, and thoughtful UX considerations.
• CHANGELOG.md requires correction to use {PR_MERGE_DATE} template string. Consider updating .eslintrc.json to eslint.config.js format for consistency with newer extensions.

Important Files Changed

File Analysis

Filename	Score	Overview
extensions/catenary-raycast/CHANGELOG.md	3/5	Changelog entry uses actual date instead of template string {PR_MERGE_DATE}
extensions/catenary-raycast/.eslintrc.json	3/5	Uses .eslintrc.json format instead of recommended eslint.config.js format
extensions/catenary-raycast/src/check-departures.tsx	5/5	Well-structured main component with proper error handling, loading states, and React best practices

[greptile-apps]

_{9 files reviewed, 2 comments}

_{Edit Code Review Agent Settings | Greptile}

[0xdhrv]

note

Thanks for your contribution. Minor suggestions and feedback added.

[0xdhrv]

fix needed

@quacksire The build is failing, can you please check it?

• https://github.com/raycast/extensions/actions/runs/19691354670/job/56407598818?pr=23129#step:7:434