MetatroncubeSoftwareSolutions/metatrondelivery

History

CI / Lint, Unit & Integration Tests (push) Has been cancelled

Details

fix: add missing react-reconciler peer dependency for checkout-datetime

@shopify/ui-extensions-react's internal @remote-ui/react dependency
requires react-reconciler as a peer dependency, which npm doesn't
auto-install — esbuild failed bundling checkout-datetime with "Could not
resolve react-reconciler" since nothing in the workspace declared it.
Added explicitly to checkout-datetime's package.json at a version
satisfying @remote-ui/react's peer range (>=0.26.0 <0.30.0); npm
workspaces hoists it to the shared root node_modules automatically,
which is where @remote-ui/react's own import resolution needs it.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>

2026-09-12 23:48:42 -04:00

locales

feat: finish multi-pin pickup end-to-end; fix checkout-datetime followups

2026-09-10 16:47:59 -04:00

src

fix: real checkout-datetime version/capability fix + payment-customization schema

2026-09-12 23:44:37 -04:00

.gitignore

feat: close DS study coverage gaps (inventory exclusion, live checkout re-validation, per-day cap, payment fn, checkout ext)

2026-09-04 01:31:02 -04:00

package.json

fix: add missing react-reconciler peer dependency for checkout-datetime

2026-09-12 23:48:42 -04:00

README.md

feat: close DS study coverage gaps (inventory exclusion, live checkout re-validation, per-day cap, payment fn, checkout ext)

2026-09-04 01:31:02 -04:00

shopify.extension.toml

fix: real checkout-datetime version/capability fix + payment-customization schema

2026-09-12 23:44:37 -04:00

tsconfig.json

feat: finish multi-pin pickup end-to-end; fix checkout-datetime followups

2026-09-10 16:47:59 -04:00

README.md

checkout-datetime

Checkout UI Extension. Three targets in one extension:

Module	Target	Plans
`src/Checkout.jsx`	`purchase.checkout.block.render`	Plus only — native in-checkout date/time picker
`src/ThankYou.jsx`	`purchase.thank-you.block.render`	all plans
`src/OrderStatus.jsx`	`customer-account.order-status.block.render`	all plans

The picker calls this app's own checkout.scheduling.availability / checkout.scheduling.hold routes (session-token auth) and draws from the same capacity pool as the storefront widget and POS. It only collects a selection into checkout attributes — the validation-slot Function is still what enforces it, so the extension is not a security boundary.

The all-plan confirmation is also covered by the theme block extensions/datetime-widget/blocks/order-confirmation.liquid; the Thank you / Order status modules here are the Plus-native version of the same thing.

Before deploy

npm --prefix extensions/checkout-datetime install (pulls @shopify/ui-extensions + preact).
In the extension's settings (Partners dashboard or shopify.extension.toml defaults), set App backend URL to the same value as application_url in shopify.app.toml — the extension runs on a different origin and needs the absolute URL to reach the backend.
shopify app deploy.

The previous build output under dist/ is gitignored and regenerated on deploy — this src/ tree is the source of record.

Type checking

tsconfig.json ships with checkJs: false because this source hasn't yet been iterated against the live @shopify/ui-extensions checkout component types (that needs the extension's deps installed and, ideally, a real checkout to verify runtime shapes — same caveat pos-datetime carries). Before deploying: npm install in this folder, flip checkJs back to true, run npm run typecheck, and reconcile the <s-*> component props against the real typings. The decision logic it depends on (resolveAvailabilityRequest, resolveHoldRequest) is already fully tested on the server side.