@genesislcap/vite-builder 15.57.0 → 15.58.1-FUI-2629.4

package/dist/index.d.ts

@@ -1,28 +1,4 @@
 import type { BuildContext } from '@genesislcap/build-kit';
-/**
- * There seems to be various documented issues using Vite in a monorepo setup that are impacted by various factors.
- *
- * Consider:
- * - npm workspace / lerna managed package links within the monorepo itself
- * - installed package dependencies that have internal dependencies (peer or otherwise) back onto the packages in this monorepo
- * - manually npm linked package dependencies that have internal (peer or otherwise) back onto the packages in this monorepo
- *
- * There are several layers of Vite configuration offered to try and combat this, but there doesn't seem to be a definitive guide.
- *
- * We've attempted to address the issue using optimizeDeps.include/exclude, resolve.dedupe, but there are several other
- * configs like build.commonjsOptions.include/exclude etc.
- *
- * Devs can continue to use the default Vite based dev task where speed of reload is desired:
- *
- * `"dev": "genx dev"`
- *
- * ...but be aware of that the integrity of the dependency graph is being compromised to simply improve build speeds.
- * You may wish to use webpack for development instead, especially if using npm link.
- *
- * `"dev:webpack": "genx dev -b webpack"`
- *
- * This has the added benefit of aligning with the current production app builds.
- */
 declare const _default: (ctx: BuildContext) => Promise<void>;
 export default _default;
 //# sourceMappingURL=index.d.ts.map

package/dist/index.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"index.d.ts","sourceRoot":"","sources":["../src/index.ts"],"names":[],"mappings":"AAEA,OAAO,KAAK,EAAE,YAAY,EAAE,MAAM,wBAAwB,CAAC;AAc3D;;;;;;;;;;;;;;;;;;;;;;;GAuBG;yBAEmB,KAAK,YAAY;AAAvC,wBAwOE"}
+{"version":3,"file":"index.d.ts","sourceRoot":"","sources":["../src/index.ts"],"names":[],"mappings":"AAEA,OAAO,KAAK,EAAE,YAAY,EAAE,MAAM,wBAAwB,CAAC;yBA0CrC,KAAK,YAAY;AAAvC,wBA0OE"}

package/dist/index.js

@@ -30,6 +30,8 @@ const vite_js_1 = require("./vite.js");
  *
  * This has the added benefit of aligning with the current production app builds.
  */
+// optimizeDeps.entries replaces Vite's default scan entries and their ignores, so restate them
+const VITE_DEFAULT_DEP_SCAN_ENTRIES = ['**/*.html', '!**/__tests__/**', '!**/coverage/**'];
 exports.default = (ctx) => tslib_1.__awaiter(void 0, void 0, void 0, function* () {
     var _a, _b, _c, _d;
     const { config: { app: { rootElement }, env, http, }, dirs: { cwd }, cli: { isDev, isBuild, isAnalyze, options: { open, https }, }, pkg: { description }, resolve: { alias }, } = ctx;
@@ -147,6 +149,8 @@ exports.default = (ctx) => tslib_1.__awaiter(void 0, void 0, void 0, function* (
         },
         root: cwd,
         optimizeDeps: {
+            // src/pbc is only imported via foundation-shell's import.meta.glob, unseen by the dep scanner
+            entries: [...VITE_DEFAULT_DEP_SCAN_ENTRIES, 'src/pbc/**/*.ts'],
             /**
              * Any external @genesislcap packages, ie. not contained within this monorepo, vite will optimize by default.
              * This behaviour creates core @genesislcap and possibly @microsoft library duplication issues. To address this,

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "@genesislcap/vite-builder",
   "description": "Vite builder",
-  "version": "15.57.0",
+  "version": "15.58.1-FUI-2629.4",
   "license": "SEE LICENSE IN license.txt",
   "main": "dist/index.js",
   "types": "dist/index.d.ts",
@@ -16,7 +16,7 @@
     "lint:fix": "genx lint -l ox --fix"
   },
   "dependencies": {
-    "@genesislcap/build-kit": "15.57.0",
+    "@genesislcap/build-kit": "15.58.1-FUI-2629.4",
     "consola": "^3.0.2",
     "copyfiles": "^2.4.1",
     "vite": "^7.2.2",