Bilal Godil 6a01e2507a fix(rde): graceful config load errors + lightweight /config import path ... The local dashboard evaluates a project's hexclave.config.ts in a plain Node context via jiti. When a config imported a value (e.g. defineStackConfig) from a framework package like @stackframe/stack / @hexclave/next, jiti executed the whole SDK (React, server-only, Next internals) and threw, surfacing only as "Failed to register development environment session (500)". - Catch jiti load failures in readConfigFile and rethrow a helpful message that points at the lightweight import path. - Add a side-effect-free `./config` subpath to the framework packages (@hexclave/{js,next,react,tanstack-start}/config) that re-exports defineHexclaveConfig/defineStackConfig + the HexclaveConfig type from @hexclave/shared/config, with no framework runtime. Users directly depend on these packages, so the subpath resolves under pnpm strict mode (unlike the transitive @hexclave/shared/config). - Point the setup prompt, hand-written docs (docs-mintlify), and the renderer that auto-writes config files at the new `<pkg>/config` path. Legacy @stackframe/* packages predate the subpath, so they keep their root import. Existing config files that import from a package root are upgraded to the /config path on their next dashboard/CLI sync.		2026-06-04 15:05:59 -07:00
..
package.json	fix(rde): graceful config load errors + lightweight /config import path	2026-06-04 15:05:59 -07:00