@poveste/plugin-quasar 0.18.3 → 0.19.1

package/README.md

@@ -6,9 +6,10 @@ Builds a Poveste book inside a Quasar project.
 pnpm add -D poveste @poveste/plugin-vue @poveste/plugin-quasar
 ```
 
-Add both plugins in poveste config:
+Add both plugins in poveste config, with a setup file:
 
 ```ts
+// poveste.config.ts
 import { HstQuasar } from '@poveste/plugin-quasar'
 import { HstVue } from '@poveste/plugin-vue'
 import { defineConfig } from 'poveste'
@@ -18,9 +19,20 @@ export default defineConfig({
     HstVue(),
     HstQuasar(),
   ],
+  setupFile: '/src/poveste.setup.ts',
 })
 ```
 
+The setup file installs Quasar into the app Poveste renders your stories in, and every Quasar component needs it, not only boot files. Without it the book still builds, and each story that uses a Quasar component shows "This component threw while rendering", with `Cannot read properties of undefined (reading 'platform')` in the browser console.
+
+```ts
+// src/poveste.setup.ts
+import { setupQuasar } from '@poveste/plugin-quasar/setup'
+import { defineSetupVue } from '@poveste/plugin-vue'
+
+export const setupVue = defineSetupVue(setupQuasar())
+```
+
 Quasar builds its Vite config asynchronously and exposes it through an
 entrypoint whose own header says it is for tooling. This plugin fetches it and
 makes the two adjustments a book needs — both of which are easy to get wrong and

package/dist/index.d.ts

@@ -48,11 +48,19 @@ export declare function withoutProcessExit<T>(fn: () => Promise<T>): Promise<T>;
  * `ssr.noExternal` is the part users should not have to know: Quasar's plugin
  * writes `__QUASAR_VERSION__` while transforming its own source, so that source
  * has to be transformed rather than externalised during story collection.
+ *
+ * `optimizeDeps.include` names Quasar because Vite's scan cannot find it: a
+ * `<q-btn>` becomes an import of `quasar` only when Quasar's plugin transforms
+ * the template. Left to be discovered, it is bundled in a second pass once the
+ * first story loads, and the page is reloaded under the reader while it runs.
  */
 export declare function quasarViteConfig(viteConfig: QuasarViteConfig): {
     ssr: {
         noExternal: RegExp[];
     };
+    optimizeDeps: {
+        include: string[];
+    };
     define: {
         [x: string]: unknown;
     };

package/dist/index.js

@@ -88,10 +88,16 @@ export async function withoutProcessExit(fn) {
  * `ssr.noExternal` is the part users should not have to know: Quasar's plugin
  * writes `__QUASAR_VERSION__` while transforming its own source, so that source
  * has to be transformed rather than externalised during story collection.
+ *
+ * `optimizeDeps.include` names Quasar because Vite's scan cannot find it: a
+ * `<q-btn>` becomes an import of `quasar` only when Quasar's plugin transforms
+ * the template. Left to be discovered, it is bundled in a second pass once the
+ * first story loads, and the page is reloaded under the reader while it runs.
  */
 export function quasarViteConfig(viteConfig) {
     return {
         ssr: { noExternal: [/quasar/] },
+        optimizeDeps: { include: ['quasar'] },
         define: { ...viteConfig.define },
         resolve: {
             alias: viteConfig.resolve?.alias,

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "@poveste/plugin-quasar",
   "type": "module",
-  "version": "0.18.3",
+  "version": "0.19.1",
   "description": "Poveste plugin that builds a book inside a Quasar project",
   "author": {
     "name": "Sorin Gitlan",
@@ -52,18 +52,18 @@
   },
   "peerDependencies": {
     "@quasar/app-vite": "^3.8.0",
-    "poveste": "^0.18.3",
+    "poveste": "^0.19.1",
     "quasar": "^2.24.0",
     "vue": "^3.5.43"
   },
   "dependencies": {
-    "@poveste/shared": "0.18.3",
+    "@poveste/shared": "0.19.1",
     "pathe": "^2.0.3"
   },
   "devDependencies": {
     "@quasar/app-vite": "^3.10.0",
     "@types/node": "^26.6.3",
-    "poveste": "0.18.3",
+    "poveste": "0.19.1",
     "quasar": "^2.33.2",
     "typescript": "6.0.3",
     "vite": "^8.3.1",