Missing Master CSS entry

The integration could not find a project CSS entry for the shared MasterCSSManifest, editor tooling, and build integration behavior.

Causes

Why this warning occurred

An integration started without finding a project CSS entry in the current project directory.

[@master/css.vite] Master CSS entry was not found in /path/to/project.Create /path/to/project/index.css and mark it as the project entry, for example:  @import "@master/css";  @import "./src/globals.css";Master CSS uses this entry graph for integrations, language service, and VS Code. Imported CSS manifest directives participate in the graph.

Master CSS can still generate utility CSS without a project entry, but integrations and editor tooling use the project CSS entry to compile the shared MasterCSSManifest for tokens, component definitions, animations, and workspace behavior.

@theme, @settings, @custom-variant, and managed definition directives do not have to be written directly in the entry file. They can live in ordinary CSS files such as src/globals.css or app/globals.css, as long as the entry imports those files with a relative CSS import. The normal app entry imports @master/css; the lightweight @master entry; marker is also recognized when a stylesheet intentionally should not load the package stylesheet graph.

Solutions

Create a workspace entry

Create index.css at the project root and import your stylesheet entry.

@import '@master/css';@import './src/globals.css';

Then keep tokens, component rules, animations, or other Master CSS manifest directives in that imported stylesheet or in files imported by it.

@theme {    --color-primary: #4f46e5;}@components {    btn {        @compose inline-flex align-items:center px:md h:40px r:md bg:primary fg:white;    }}

Ordinary CSS outside Master CSS directives stays native CSS and follows the integration's stylesheet behavior.

Import an explicit manifest resource

If runtime code should intentionally use one CSS resource instead of the discovered project-level entry, import that resource with ?master-css-manifest.

import { CSSRuntime } from '@master/css-runtime'import manifest from './theme.css?master-css-manifest'CSSRuntime.create({ manifest }).observe()

For lower-level APIs that accept a compiled manifest directly, pass a MasterCSSManifest through their manifest option.

Ignore the warning

You can ignore this warning when the current project intentionally has no project CSS entry and does not need shared tokens, component definitions, animations, language-service workspace detection, or editor integration behavior.