fix: preserve plugin manifest compatibility

2026-07-13 12:29:21 +02:00
parent 0d3096973e
commit a9bcfe25ff
7 changed files with 36 additions and 22 deletions
@@ -395,10 +395,12 @@ After editing, check the manifest endpoint and browser-console failure cases.</c
                the remote machine exposes its own copy.
              </p>
              <p>
-                Current PI WEB manifests publish module references relative to the fetched manifest, so local and
-                federated plugin modules follow root or nested reverse-proxy deployments without a prefix-specific
-                build. The browser and federated gateway also accept leading-root module references emitted by existing
-                PI WEB releases and keep them inside the current application base.
+                Current PI WEB manifests publish leading application-root module references. The browser keeps them
+                inside the current application base, so local and federated plugins follow root or nested reverse-proxy
+                deployments without a prefix-specific build while remaining compatible with existing gateways.
+                Federated gateways also accept manifest-relative references such as
+                <code>./&lt;plugin-id&gt;/plugin.js</code> and legacy plugin-root-relative references such as
+                <code>nested/plugin.js</code> from remote machines.
              </p>
              <p>
                For portable plugin assets, prefer URLs relative to the plugin module, such as