DF0069: Service Version Range Not Satisfied

Message

The installed service "{package}@{installed}" does not satisfy the declared range "{required}" — installing it anyway.

Cause

A service descriptor declares a version range, and the version of the service that actually resolved falls outside it. Since the descriptor isn't marked required, the service still installs — the range acts as a compatibility hint, and this warning surfaces the drift. The advertised meta carries the real version, so client UIs can gate features on it.

The required: true variant of the same mismatch throws DF0068 instead.

Example

defineDevframe({
  services: [
    // Installed: @devframes/service-shiki@2.0.0 → warns, still installs.
    { package: '@devframes/service-shiki', version: '^1' },
  ],
})

Fix

Align the installed service package with the declared range to silence the warning, or widen the declared range when the newer service is actually fine.

Source

• packages/devframe/src/node/host-services.ts — the pre-setup construction checks each descriptor's version range against the resolved definition.