PHPackages                             prior-notify/upward-connector - PHPackages - PHPackages  [Skip to content](#main-content)[PHPackages](/)[Directory](/)[Categories](/categories)[Trending](/trending)[Leaderboard](/leaderboard)[Changelog](/changelog)[Analyze](/analyze)[Collections](/collections)[Log in](/login)[Sign up](/register)

1. [Directory](/)
2. /
3. [Utility & Helpers](/categories/utility)
4. /
5. prior-notify/upward-connector

ActiveMagento2-module[Utility & Helpers](/categories/utility)

prior-notify/upward-connector
=============================

PriorNotify module used for routing all frontend requests through UPWARD-PHP.

1.4(4y ago)08OSL-3.0PHPPHP ~7.3.0||~7.4.0

Since Jun 24Pushed 4y ago1 watchersCompare

[ Source](https://github.com/a-kravchuk-bit/PN)[ Packagist](https://packagist.org/packages/prior-notify/upward-connector)[ RSS](/packages/prior-notify-upward-connector/feed)WikiDiscussions main Synced today

READMEChangelog (5)Dependencies (7)Versions (7)Used By (0)

Magento 2 UPWARD connector module
=================================

[](#magento-2-upward-connector-module)

The Magento 2 UPWARD connector is a module for routing requests to [UPWARD-PHP](https://github.com/magento/upward-php). This module replaces the default Magento frontend theme with a PWA Studio storefront application.

PWA Studio storefront deployments in the Magento Commerce Cloud use this module to keep Magento and storefront code on the same server.

Installation
------------

[](#installation)

The Magento 2 UPWARD connector module is part of the [Magento Cloud deployment](http://pwastudio.io/tutorials/cloud-deploy/) steps in the official PWA Studio docs.

Configuration
-------------

[](#configuration)

The Magento 2 UPWARD connector has additional settings that can be configured in the admin area under:

**Stores > Configuration > General > Web > UPWARD PWA Configuration**.

### General configuration

[](#general-configuration)

These are the configurations for the UPWARD process itself.

#### UPWARD Config File

[](#upward-config-file)

This configuration is the location of the UPWARD configuration file for the UPWARD-PHP server. It is recommended you follow [system-specific best practices](https://devdocs.magento.com/guides/v2.4/config-guide/prod/config-reference-var-name.html) and set this value with an environment variable or the `magento config:set` CLI command.

*You may use a path relative to your web root or an absolute path for the value of this configuration.*

Relative: `fastcgi_param CONFIG__DEFAULT__WEB__UPWARD__PATH pwa/upward.yml`Absolute: `magento config:set -e web/upward/path /app/node_modules/@magento/venia-concept/dist/upward.yml`

#### Front Name Allowlist

[](#front-name-allowlist)

This configuration allows you to specify a line-separated list of routes to forward to the default Magento theme.

Example:

```
contact
privacy-policy-cookie-restriction-mode

```

With this example, when a visitor navigates to either `/contact` or `/privacy-policy-cookie-restriction-mode`, they will land on a page rendered by Magento instead of the storefront application.

### Prerender.io Configuration

[](#prerenderio-configuration)

[Prerender.io](https://docs.prerender.io/) support in the upward-connector module allows your site to send prerendered static html to search bots.

A middleware layer checks each request to see if it comes from a crawler and if allowed, sends it to the prerender service. These configuration entries let you configure which pages to send to Prerender.io to serve the static HTML versions of that page. If a page is not configured for prerendering, the request continues using the normal server routes.

ConfigurationDescriptionExampleEnable Prerender For Search BotsThis enables prerender functionality for this store view.Prerender URLUrl of the prerender service.Prerender.io TokenToken to use for the prenderer.io hosted serviceCrawler User AgentsLine break separated list of keywords to detect the crawler in the user-agent request headerBlocked ListResources that will not be sent for prerendering. Use `*` as a wildcard character.`.js` `*/cart`Allowed ListExplicitly allowed resources to be sent for prerendering. If empty, all resources are allowed.#### Testing prerendered pages

[](#testing-prerendered-pages)

To see how a crawler sees a prerendered page, set your browser's User Agent to `Googlebot` and visit your URL. You can also run this on the command line and change the sample URL to your storefront's URL:

```
curl -A Googlebot https://www.example.com/ > page.html
```

To configure prerender locally for testing purposes, see .

#### Troubleshooting partial rendered pages

[](#troubleshooting-partial-rendered-pages)

There is no way to tell when a PWA page fully loads. For prerendering it is possible to force prerender to wait for a predefined timeout before setting the `window.prerenderReady` flag.

Add the following to the runtime script:

```
window.prerenderReady = false;
setTimeout(function () {
  window.prerenderReady = true;
}, 1000 * 15);
```

For more information, see .

Service Worker Note
-------------------

[](#service-worker-note)

Avoid sharing the same hostname between your PWA Studio storefront and the Magento 2 admin backend. This causes the storefront Service Worker to intercept backend requests when you have both the storefront and admin tabs open at the same time on your browser. If you cannot avoid sharing the hostname, access one service at a time or use a private browsing session per service.

###  Health Score

24

—

LowBetter than 32% of packages

Maintenance20

Infrequent updates — may be unmaintained

Popularity4

Limited adoption so far

Community7

Small or concentrated contributor base

Maturity56

Maturing project, gaining track record

 Bus Factor1

Top contributor holds 100% of commits — single point of failure

How is this calculated?**Maintenance (25%)** — Last commit recency, latest release date, and issue-to-star ratio. Uses a 2-year decay window.

**Popularity (30%)** — Total and monthly downloads, GitHub stars, and forks. Logarithmic scaling prevents top-heavy scores.

**Community (15%)** — Contributors, dependents, forks, watchers, and maintainers. Measures real ecosystem engagement.

**Maturity (30%)** — Project age, version count, PHP version support, and release stability.

###  Release Activity

Cadence

Every ~8 days

Total

5

Last Release

1749d ago

### Community

Maintainers

![](https://avatars.githubusercontent.com/u/73112691?v=4)[a-kravchuk-bit](/maintainers/a-kravchuk-bit)[@a-kravchuk-bit](https://github.com/a-kravchuk-bit)

---

Top Contributors

[![incora-dev](https://avatars.githubusercontent.com/u/36540892?v=4)](https://github.com/incora-dev "incora-dev (5 commits)")

### Embed Badge

![Health badge](/badges/prior-notify-upward-connector/health.svg)

```
[![Health](https://phpackages.com/badges/prior-notify-upward-connector/health.svg)](https://phpackages.com/packages/prior-notify-upward-connector)
```

###  Alternatives

[fastly/magento2

Fastly CDN Module for Magento 2.4.x

1564.2M1](/packages/fastly-magento2)[baldwin/magento2-module-url-data-integrity-checker

Magento 2 module which can find potential url related problems in your catalog data

281773.3k](/packages/baldwin-magento2-module-url-data-integrity-checker)[yireo/magento2-webp2

Magento 2 module to add WebP support to the Magento frontend

2091.2M7](/packages/yireo-magento2-webp2)

PHPackages © 2026

[Directory](/)[Categories](/categories)[Trending](/trending)[Changelog](/changelog)[Analyze](/analyze)