Problem: the hexagonal refactor churns the backend tree for nine more phases; the UI delivery stack (web/ SPA, cmd/desktop Wails wrapper, compose/web image) must move to its own repo first so doc/layout rewrites land once on a backend-only tree. Change: - New repo git.hubris.network/dtoro/oikos-web (v0.33.0): web/, desktop/ (updateURL repointed to oikos-web releases), compose/, own CI (web + desktop jobs), own deploy script (CI-green gate, TOCTOU guard, version-tagged images, prune-to-3), own webhook receiver on :9798 + launchd unit, own compose project publishing the same 8091:80. - Cutover executed on mac-mini in order: oikos stack's web service stopped+removed, oikos-web project brought up on 8091; outer Caddy untouched (targets the published port) — serving + Authentik flow + /wails 404 quirk verified post-cutover. - Stripped from oikos: web/, cmd/desktop/, compose/web/, desktop CI workflow, ci.yml web job, Makefile ui/desktop/desktop-package/install targets, the compose web service, oikos-web from deploy.sh's fallback prune list; wails + go-keyring dropped from go.mod, vendor synced. - README / CONTRIBUTING / AGENTS.md / .agents dev+operations docs now point at the new repo; mbse + mascot design docs carry a path note. Risk: production SPA serving depends on the new pipeline now; rollback is versioned-image re-up of the old web service from a pre-split checkout (port 8091). Desktop builds installed before the split still check dtoro/oikos releases — one manual reinstall, noted in the oikos-web release notes. Verification: go vet, make test (race), make generate-check, golangci (no new findings; baseline down 400→365); post-cutover curls — localhost:8091 200, /wails/runtime.js 404, outer Caddy 302 Authentik.
44 lines
1.4 KiB
JavaScript
44 lines
1.4 KiB
JavaScript
/**
|
|
* Utility for resolving a module relative to another module
|
|
* @author Teddy Katz
|
|
*/
|
|
|
|
import Module from "node:module";
|
|
|
|
/*
|
|
* `Module.createRequire` is added in v12.2.0. It supports URL as well.
|
|
* We only support the case where the argument is a filepath, not a URL.
|
|
*/
|
|
const createRequire = Module.createRequire;
|
|
|
|
/**
|
|
* Resolves a Node module relative to another module
|
|
* @param {string} moduleName The name of a Node module, or a path to a Node module.
|
|
* @param {string} relativeToPath An absolute path indicating the module that `moduleName` should be resolved relative to. This must be
|
|
* a file rather than a directory, but the file need not actually exist.
|
|
* @returns {string} The absolute path that would result from calling `require.resolve(moduleName)` in a file located at `relativeToPath`
|
|
* @throws {Error} When the module cannot be resolved.
|
|
*/
|
|
function resolve(moduleName, relativeToPath) {
|
|
try {
|
|
return createRequire(relativeToPath).resolve(moduleName);
|
|
} catch (error) {
|
|
|
|
// This `if` block is for older Node.js than 12.0.0. We can remove this block in the future.
|
|
if (
|
|
typeof error === "object" &&
|
|
error !== null &&
|
|
error.code === "MODULE_NOT_FOUND" &&
|
|
!error.requireStack &&
|
|
error.message.includes(moduleName)
|
|
) {
|
|
error.message += `\nRequire stack:\n- ${relativeToPath}`;
|
|
}
|
|
throw error;
|
|
}
|
|
}
|
|
|
|
export {
|
|
resolve
|
|
};
|