@quazardous/qdadm 1.19.3 → 1.19.4
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +21 -0
- package/package.json +3 -1
package/README.md
CHANGED
|
@@ -106,6 +106,27 @@ Options: `transformRequest`, `transformResponse`, `responseFormat`, `clientSideP
|
|
|
106
106
|
- primevue ^4.0.0
|
|
107
107
|
- pinia ^2.0.0
|
|
108
108
|
|
|
109
|
+
## Consuming via `file:` link from a sibling monorepo
|
|
110
|
+
|
|
111
|
+
If you install qdadm with a `file:../path/to/qdadm` link instead of from npm — typically during local development on qdadm itself, or before a release lands — pnpm/npm resolves the symlink into the qdadm-monorepo's hoisted `node_modules`. That can pull a *second* copy of `primevue` (and `vue`, `vue-router`, `@primeuix/themes`) into your host bundle even though qdadm itself only declares them as peers.
|
|
112
|
+
|
|
113
|
+
Symptom: PrimeVue components render without their Aura preset tokens — component-level CSS variables (`--p-paginator-nav-button-width`, etc.) end up undefined, so paginator buttons collapse to 16×16, datatables lose padding, rounded corners disappear. Plugin singletons rely on a shared runtime registry; two instances split the registry in half.
|
|
114
|
+
|
|
115
|
+
Fix in the host's bundler config — `dedupe` collapses duplicates back to a single resolved copy:
|
|
116
|
+
|
|
117
|
+
```ts
|
|
118
|
+
// vite.config.ts
|
|
119
|
+
export default defineConfig({
|
|
120
|
+
resolve: {
|
|
121
|
+
dedupe: ['vue', 'vue-router', 'primevue', '@primeuix/themes'],
|
|
122
|
+
},
|
|
123
|
+
})
|
|
124
|
+
```
|
|
125
|
+
|
|
126
|
+
This is the canonical Vite/Webpack pattern for Vue plugin singletons. The `file:` link can stay in place — useful for hot-reload during qdadm development — and the dedupe ensures only one instance of each peer ends up in the bundle.
|
|
127
|
+
|
|
128
|
+
Installing qdadm from npm (`@quazardous/qdadm@^1.19.3`) doesn't have this issue: the published tarball ships no `node_modules/`, so peers always resolve from the host. The trap is specific to `file:` / `workspace:` links onto a package that lives inside another monorepo.
|
|
129
|
+
|
|
109
130
|
## License
|
|
110
131
|
|
|
111
132
|
MIT
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@quazardous/qdadm",
|
|
3
|
-
"version": "1.19.
|
|
3
|
+
"version": "1.19.4",
|
|
4
4
|
"description": "Vue 3 framework for admin dashboards with PrimeVue",
|
|
5
5
|
"author": "quazardous",
|
|
6
6
|
"license": "MIT",
|
|
@@ -81,6 +81,7 @@
|
|
|
81
81
|
],
|
|
82
82
|
"devDependencies": {
|
|
83
83
|
"@eslint/js": "^9.39.2",
|
|
84
|
+
"@primeuix/themes": "^1.0.0",
|
|
84
85
|
"@types/node": "^25.0.6",
|
|
85
86
|
"@vitejs/plugin-vue": "^6.0.0",
|
|
86
87
|
"@vue/test-utils": "^2.4.6",
|
|
@@ -92,6 +93,7 @@
|
|
|
92
93
|
"globals": "^17.0.0",
|
|
93
94
|
"jsdom": "^25.0.1",
|
|
94
95
|
"prettier": "^3.7.4",
|
|
96
|
+
"primevue": "^4.0.0",
|
|
95
97
|
"sass": "^1.97.1",
|
|
96
98
|
"typescript": "^5.9.3",
|
|
97
99
|
"typescript-eslint": "^8.52.0",
|