feat(apps): apps-engine split, dynamic import apps
Closed
D-
5mo ago+281+281+012345678901234567890123456789-205-205-012345678901234567890123456789
Proposed changes (including videos or screenshots)
This PR adapts the path resolution of the apps-engine package for the deno runtime. Some assumptions changed:
- Previously the deno runtime controller resolved apps-engine paths relatively, as it lived inside the package. This allowed for some flexibility in deno's import map. But now that the runtime lives outside the engine, the controller doesn't know the path to this other package, so we have to inject the resolved path in the import map at runtime instead of statically.
- The deno process now uses "sloppy imports" to import files from the apps-engine and apps packages.
Issue(s)
Steps to test or reproduce
Further comments
Related to the "Apps-Engine split" stack:
Deprecated
Summary by CodeRabbit
-
Refactor
- Makes runtime configuration generation location-independent to improve app startup and import resolution.
-
Chores
- Updates runtime/config handling and lint settings to align with new import behavior; ignores the runtime-generated config file.