We’re customizing Frappe Insights (v3.x) to add an Oracle backend UI. All of our custom Vue components live in a separate app (customapp). The backend overrides were easy, but we’re stuck on the frontend build: the files we’re overriding (frontend/src2/data_source DataSourceList.vue, data_source.ts, data_source.types.ts, ConnectOracleDialog.vue, components/Icons/OracleIcon.vue) are imported with relative paths (./ConnectOracleDialog.vue). Vite resolves those immediately inside apps/insights, so aliases or hooks in our custom app never get a chance to redirect them.
Right now the only way to build successfully is to copy our “customapp” versions into apps/insights/frontend/src2/… before bench build and then restore the repo afterwards (we wrapped this in a script). That works, but it’s brittle—we can’t run bench build directly and we’d prefer to keep apps/insights clean.
Has anyone found a cleaner way to override Vue SFCs that are imported via relative paths in Insights? Ideally we’d like to keep the files in our custom app, but Vite doesn’t seem to allow intercepting ./ imports without patching the upstream files. Any guidance or best practices from others who’ve done similar monkey patches would be appreciated.