Add woocommerce-quicker extension

[g-mai]

Description

WooCommerce Quicker lets users quickly search their WooCommerce stores for orders, customers, and products.

Commands:

• Search Orders: filter by status, searches in multiple fields, press Enter to open in browser
• Search Customers: filter by role, search by name or email, press Enter to open in browser
• Search Products: filter by status, shows price, type, stock status
• Manage Stores: add, edit, and delete multiple stores with credential validation

Key features:

• Multi-store support
• Credentials validated against the WooCommerce API before saving
• Support for local/self-signed SSL stores (development use)

Notes for reviewers

If you check the useStores.ts custom hook you'll see that I'm using useLocalStorage to save authentication credentials. I'm aware the guidelines mention to use the Preferences API for things like keys and authentication credentials, but I couldn't find a way to do that while supporting multiple stores and make it a good experience for the user.

In the other custom hook, useWooCommerce.ts, I import fetch from "cross-fetch" instead of using the built in fetch or raycast's useFetch, because both of them were failing when calling a local Wordpress with a self-signed SSL certificate. The easiest solution I found was to add an option to the stores that, when checked, allows the hook to use cross-fetch fetch, with a custom agent that ignores SSL errors.

The rest of the extension is just basic fetches and list results, nothing really special about it.

Screencast

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! 🚀

We're currently experiencing a high volume of incoming requests. As a result, the initial review may take up to 10-15 business days.

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

[greptile-apps]

Greptile Summary

This PR adds the woocommerce-quicker extension, providing multi-store WooCommerce search for orders, customers, and products with credential validation and local SSL support. Previous review feedback on error handling, the cancel toast, and the cross-fetch comment has been addressed — one item from that round still needs a one-line fix.

• CHANGELOG date: 2026-04-30 is still a hardcoded date; the {PR_MERGE_DATE} placeholder was not actually applied despite the "fixed" reply.

Confidence Score: 4/5

Safe to merge after fixing the CHANGELOG placeholder — no runtime bugs found in the core extension logic.

One P1 finding (hardcoded changelog date) and one P2 (inconsistent null guard), neither of which affect runtime behavior. Core logic — API fetching, error handling, store CRUD, and credential validation — is correct and clean.

CHANGELOG.md (hardcoded date), src/hooks/useWooCommerce.ts (minor null-guard inconsistency)

Important Files Changed

Filename	Overview
extensions/woocommerce-quicker/CHANGELOG.md	Still uses a hardcoded date (2026-04-30) instead of the required {PR_MERGE_DATE} template placeholder.
extensions/woocommerce-quicker/src/hooks/useWooCommerce.ts	Error-parsing logic correctly restructured from previous review; minor inconsistency between null guards on lines 25–26 and unchecked store.local access on line 42.
extensions/woocommerce-quicker/src/hooks/useStores.ts	Clean local-storage hook with CRUD + favorite-sort logic; no issues found.
extensions/woocommerce-quicker/src/components/store-form.tsx	Validates credentials against the live API before saving; correctly decodes HTML entity currency symbols with he.
extensions/woocommerce-quicker/package.json	All declared dependencies (cross-fetch, he, @raycast/utils) are actually used in source files; schema reference and platforms are correctly set.
extensions/woocommerce-quicker/src/manage-stores.tsx	Delete confirmation with destructive alert style; cancel toast removed per previous review feedback.

Prompt To Fix All With AI

Fix the following 2 code review issues. Work through them one at a time, proposing concise fixes.

---

### Issue 1 of 2
extensions/woocommerce-quicker/CHANGELOG.md:3
**Hardcoded date still present after fix attempt**

The previous review flagged `2026-04-12` and the reply was "fixed in latest commit", but the current file has `2026-04-30` — still a hardcoded date rather than the `{PR_MERGE_DATE}` template placeholder. Raycast automatically substitutes this variable at merge time; a hardcoded date will never update.

```suggestion
## [Initial Version] - {PR_MERGE_DATE}
```

### Issue 2 of 2
extensions/woocommerce-quicker/src/hooks/useWooCommerce.ts:42
**Inconsistent null-guard on `store`**

Lines 25–26 defensively guard `store ?` before accessing its properties, but line 42 accesses `store.local` unconditionally. If `store` is ever falsy at runtime (even though TypeScript types it as non-null), this line throws a `TypeError` while the earlier guards would have silently recovered. Either remove the guards above (if `store` is truly always non-null) or add the same guard here.

```suggestion
  const activeRequest = store?.local ? localRequest : remoteRequest;
```

_{Reviews (5): Last reviewed commit: "Update CHANGELOG.md and optimise images" | Re-trigger Greptile}

[g-mai]

All suggestions from greptile bot have been handled in the latest commit.

[0xdhrv]

nitpick: you can use mock-data for screenshots to avoid blur

[0xdhrv]

Looks good to me, approved ✅

[github-actions]

Published to the Raycast Store:
https://raycast.com/g-mai/woocommerce-quicker

[raycastbot]

🎉 🎉 🎉

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

[greptile-apps]

Hardcoded date still present after fix attempt

The previous review flagged 2026-04-12 and the reply was "fixed in latest commit", but the current file has 2026-04-30 — still a hardcoded date rather than the {PR_MERGE_DATE} template placeholder. Raycast automatically substitutes this variable at merge time; a hardcoded date will never update.

Suggested change

	## [Initial Version] - 2026-04-30
	## [Initial Version] - {PR_MERGE_DATE}

Rule Used: What: In Raycast extension changelogs, `{PR_MERGE_... (source)

Prompt To Fix With AI

This is a comment left during a code review.
Path: extensions/woocommerce-quicker/CHANGELOG.md
Line: 3

Comment:
**Hardcoded date still present after fix attempt**

The previous review flagged `2026-04-12` and the reply was "fixed in latest commit", but the current file has `2026-04-30` — still a hardcoded date rather than the `{PR_MERGE_DATE}` template placeholder. Raycast automatically substitutes this variable at merge time; a hardcoded date will never update.

```suggestion
## [Initial Version] - {PR_MERGE_DATE}
```

**Rule Used:** What: In Raycast extension changelogs, `{PR_MERGE_... ([source](https://app.greptile.com/review/custom-context?memory=799af734-ebd9-4b40-9ffd-97a70fc71c8a))

How can I resolve this? If you propose a fix, please make it concise.