---
title: "DF0067: Required Service Package Not Importable"
description: "Failed to import the required service package \"{package}\": {reason}"
canonical_url: "https://devfra.me/errors/df0067"
---
# DF0067: Required Service Package Not Importable

> Failed to import the required service package "\{package}": \{reason}

## Message

> Failed to import the required service package "`{package}`": `{reason}`

## Cause

A service descriptor marked `required: true` names a package that could not be resolved and imported when services are constructed before setup. Descriptors resolve against the declaring devframe's own dependencies first (then the workspace root), so the package is usually missing from the declarer's `dependencies` or isn't installed. Descriptors without `required` degrade instead: the missing service is skipped and consumers observe `services.has(pkg) === false`.

## Example

```ts
defineDevframe({
  services: [
    // ✗ Throws before setup when the package isn't installed.
    { package: '@devframes/service-shiki', required: true },
  ],
})
```

## Fix

Install the service package next to whoever declares it (a devframe declaring it in `services` lists it in its own `dependencies` or `peerDependencies`), or drop `required: true` and let the consuming UI fall back when the service is absent.

## Source

- [`packages/devframe/src/node/host-services.ts`](https://github.com/devframes/devframe/blob/main/packages/devframe/src/node/host-services.ts): the pre-setup construction throws when a `required` descriptor's package fails to import.


## Sitemap

See the full [sitemap](https://devfra.me/sitemap.md) for all pages.