@poveste/vendors 0.16.0 → 0.16.2

package/README.md

@@ -10,10 +10,22 @@ dependency of `poveste` and there is nothing to install or configure directly. I
 ## One copy, or two
 
 The chrome imports Vue from here rather than by name so that it runs Poveste's copy
-and not the reader's. That is version-dependent, and it was not always: the entries
-re-export the real packages now, so when a consumer's Vue satisfies our range both
-resolve to the **same** copy, and only a consumer on a range we cannot satisfy gets a
-separate nested one.
+and not the reader's. Whether that is the reader's copy too is version-dependent, and
+it was not always.
+
+**The re-export is not what makes it one copy.** Each entry's name is an npm alias —
+`poveste-vue` is `npm:vue` — and an alias is a distinct package name, so a package
+manager installs a second physical copy of Vue whatever the consumer already has. A
+satisfied range does not collapse them and `resolve.dedupe` cannot, because it matches
+on the name. This file used to claim the opposite; two copies then meant two reactivity
+systems, and a consumer's `poveste dev` rendered no story at all (#1060).
+
+What makes it one copy is an alias `poveste` adds to a consumer's Vite config:
+`collapseVendoredVue` points `poveste-vue` at the consumer's `vue` when both are
+present and their majors agree. So when a consumer's Vue satisfies our range both do
+resolve to the **same** copy, and only a consumer on a range we cannot satisfy keeps
+the separate nested one — but by that alias, not by the shape of these entries.
+Deleting it as redundant to this paragraph reopens the defect.
 
 The two-app design is unaffected — `global-components.ts` still creates its own app and
 hands off through the DOM. What is no longer structurally true is that Poveste's chrome

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "@poveste/vendors",
   "type": "module",
-  "version": "0.16.0",
+  "version": "0.16.2",
   "description": "Poveste-owned copies of the libraries its chrome runs on",
   "author": {
     "name": "Sorin Gitlan",

package/vue.js

@@ -3,7 +3,15 @@
 // entry comes out empty — `isRef is not a function` at the first call. The npm
 // alias in this package's manifest is a name nothing remaps.
 //
-// This resolves to the *consumer's* Vue whenever theirs satisfies our range, and to a
-// nested copy only when it does not. The chrome running Poveste's own Vue is therefore
-// version-dependent rather than structural. See the README.
+// **This re-export does not by itself give the chrome the consumer's Vue, and the
+// comment that said it did is what #1060 was.** `poveste-vue` is an npm alias, so
+// it is a distinct package name and a package manager installs a second physical
+// copy whatever the consumer has — a satisfied range does not collapse them, and
+// Vite's `resolve.dedupe` cannot, because it matches on the name. Two copies is two
+// reactivity systems, and a consumer's `poveste dev` rendered no story at all.
+//
+// What collapses them is `collapseVendoredVue` in `poveste`, which aliases
+// `poveste-vue` to the consumer's `vue` on the consumer path when both are present
+// and their majors agree. So the property holds by that alias, not by the shape of
+// this file: removing it as redundant to this comment reopens #1060. See the README.
 export * from 'poveste-vue'