directus-main — known gaps
Every item below is a real, current gap — not a hedge. Some are blocked on real source landing elsewhere, some are waiting on this repo's own decisions, and some are just facts worth stating plainly rather than letting a reader assume more works than actually does. See Yarn Migration for the five gaps already found and fixed, and one still open, in the manifest layer itself.
37 of 40 workspace packages have no real source yet
This is the main body of remaining work, not a footnote — see
System Architecture
for the layer breakdown and
Package Manifests
for every package's real role. Even the 3 packages with real source have caveats:
directus
's complete source tree can't actually run yet (imports 2 manifest-only packages),
packages/types
is complete (56/56) but doesn't type-check as a whole until 3 still-manifest-only cross-package dependencies land,
and
packages/schema
itself is only 3 of 16 files in.
vitest 3.2.7→4.1.10 compatibility unverified
Bumped to latest across all 32 consuming packages by deliberate choice, but no package's
vitest.config.ts
has been copied over yet — real config compatibility with the breaking 4.x line is genuinely unconfirmed, not just
assumed fine. The VS Code Vitest extension is disabled workspace-wide for the same reason: it threw
Error: The extension could not load any config
on every launch, confirmed via a full repo search finding zero config files anywhere. Re-enable both once the
first package lands one.
blackbox.yml / e2e.yml — Run tests steps gated if: false
tests/blackbox
and
tests/e2e
are manifest-only — nothing real to run yet.
Checkout
/
Prepare
/service-startup steps stay active (still catch real regressions in install/build/docker-compose config); only
Run tests
is gated, with the re-enable condition written directly in each workflow's own comment. Tracked as
Issue #30
so it doesn't get forgotten once the source lands.
CI secrets not yet configured
Check
installs cleanly (see the
isolated-vm
fix in
Yarn Migration
), but workflows depending on secrets (
CLAUDE_CODE_OAUTH_TOKEN
,
RELEASE_PAT
,
DOCKERHUB_USERNAME
/
PASSWORD
,
SLACK_WEBHOOK_CMS_FREEZE
) aren't configured on this repo yet — e.g.
Sync Readme to Docker Hub
will keep failing until those are set. A one-time setup task, not a code gap.
Neither Dockerfile has been build-tested end-to-end
Needs the real source trees, the
isolated-vm
fix (already in), and a real run of
scripts/deploy-production.mjs
to confirm the assembled
dist/
actually boots. The script itself was already verified in isolation — see
Yarn Migration
's deploy-script correction — but a full container boot hasn't been tried yet.
isolated-vm@5.0.3 incompatible with Node 26
Failed to compile identically on Windows and the GitHub Actions Ubuntu runner — real compiler output showed the
native addon calling V8 APIs Node 26's bundled V8 has since removed or changed. Not a missing-toolchain problem —
every other native module in the dependency graph built cleanly. Fixed by bumping to
7.0.1
, verified with a real
yarn install
. Full detail on
Yarn Migration
.
Every item on this page links back to either
todo.md
's "Still to do" table or a real GitHub issue — nothing here is asserted without something to check it against.
See
todo.md
for the live, evidence-linked version.