Core is not a module

Error: Invalid dependency: “@stnd/core” is the orchestration engine, not a module.

The Problem

A module definition file declared core or @stnd/core within its dependencies array.

// index.module.js
export default {
  id: “my-module”,
  name: “My Module”,
  dependencies: [“core”] // <— The issue
};

The Why

In the Standard System, @stnd/core is the foundational integration (the orchestrator) that powers the entire module loader and lifecycle hook system. It evaluates module manifests, resolves their dependencies, and compiles them.

Because @stnd/core is an Astro integration and not a standard module, it does not export a default.id manifest property. If you instruct the module loader to treat it as a dependency, the loader attempts to resolve it like a standard module and throws a fatal error when it cannot find a valid manifest ID.

Since every module implicitly relies on the core engine to be loaded in the first place, declaring it as a dependency is both unnecessary and invalid.

The Solution

Simply remove “core” or “@stnd/core” from your module’s dependencies array.

// index.module.js
export default {
  id: “my-module”,
  name: “My Module”,
  // Remove or update the dependencies array
};