Search by

bluefairy / module-one-step-checkout-hyva

bluefairydevelopment

BlueFairy One Step Checkout - Alpine.js storefront for Hyva themes

Package info

github.com/bluefairydevelopment/module-one-step-checkout-hyva

Type:magento2-module

pkg:composer/bluefairy/module-one-step-checkout-hyva

Statistics

Installs: 0

Dependents: 0

Suggesters: 0

Stars: 0

Open Issues: 0

1.0.3 2026-11-14 15:36 UTC

This package is auto-updated.

Last update: 2026-11-15 03:06:47 UTC


README

The Alpine.js storefront of BlueFairy One Step Checkout for Hyvä themes.

Package bluefairy/module-one-step-checkout-hyva
Module BlueFairy_OneStepCheckoutHyva
Requires bluefairy/module-one-step-checkout, hyva-themes/magento2-theme-module 1.5 or later
Magento Open Source and Adobe Commerce 2.4.8 and 2.4.9
PHP 8.3, 8.4, 8.5
Licence MIT

Install

This package comes from the same Private Packagist repository as the base package bluefairy/module-one-step-checkout. Configure the repository and your credentials first, as the base package's README describes, then:

composer require bluefairy/module-one-step-checkout-hyva
bin/magento module:enable BlueFairy_OneStepCheckoutHyva
bin/magento setup:upgrade
bin/magento setup:di:compile
bin/magento setup:static-content:deploy -f
bin/magento cache:flush

There is nothing to configure here. Every setting is the base module's: Stores > Configuration > Sales > One Step Checkout. With One Step Checkout enabled, a store view on a Hyvä theme gets this checkout and a Luma store view gets the base module's.

What it needs from the theme

  • The checkout page must be served by the Hyvä theme. A store that sends /checkout to a Luma fallback theme gets the base module's Luma checkout there instead.
  • No Tailwind rebuild: the checkout uses the base module's own stylesheet.
  • Hyvä Checkout is not required and is not used. Do not enable One Step Checkout on a store view where Hyvä Checkout serves the checkout page.

Strict Content Security Policy

The template has no inline script, and every Alpine attribute names a property or a method of the component, so it runs under the Alpine CSP build Hyvä uses in strict mode.

Signing in a guest whose email has an account

As in the base module: when Magento's Sales > Checkout > Checkout Options > Enable Guest Checkout Login is Yes and a guest types an email that has an account, the contact step offers a password field and Sign In; the page reloads as the customer, and guest checkout stays open. With the setting No (Magento's default) only the "Already have an account? Sign in" link is shown. See the base module's README for the details.

Payment methods

As in the base module (see its README, "Payment methods"): Check / Money Order, Bank Transfer Payment, Cash On Delivery, Purchase Order and Zero Subtotal Checkout are built in; Stripe's Payment Element is shown when the Stripe module (StripeIntegration_Payments 4.6) is installed and enabled; third-party methods that need nothing typed are offered once listed under Other Payment Methods; any other method needs a payment renderer registered in window.bluefairyOscPayments before the checkout starts.

The Stripe card form lives in its own element, outside the part of the page Alpine redraws (x-ignore), so the card typed stays put. Stripe.js comes from js.stripe.com, which the Stripe module's CSP whitelist allows, so the form also works under the strict policy.

Uninstall

This package stores nothing of its own. Remove it on its own:

bin/magento module:uninstall BlueFairy_OneStepCheckoutHyva

or together with the base, as the base package's README describes.

Support

support@bluefairydevelopment.com