moeru-ai/airi · info
The entrypoint you imported for ${name} doesn't have any exp
Error message
The entrypoint you imported for ${name} doesn't have any exports. Try importing ${name}/pages instead. What it means
Identical guard pattern in @proj-airi/stage-pages: the root entry has no exports and only prints this warning. The actual shared page bases are exported from the /pages subpath; importing the root gives you nothing.
Source
Thrown at packages/stage-pages/src/index.ts:3
import { name } from '../package.json'
console.warn(`The entrypoint you imported for ${name} doesn't have any exports. Try importing ${name}/pages instead.`)
View on GitHub (pinned to 677329427f)
Solutions
- Change the specifier to '@proj-airi/stage-pages/pages'
- Search the monorepo for remaining root imports and correct them
- Restrict the root specifier with import/no-restricted-imports
Example fix
// before
import { ChatPageBase } from '@proj-airi/stage-pages'
// after
import { ChatPageBase } from '@proj-airi/stage-pages/pages' Defensive patterns
Strategy: validation
Validate before calling
'import/no-restricted-imports': ['error', {
paths: [{ name: '@proj-airi/stage-pages', message: 'import @proj-airi/stage-pages/pages instead' }],
}] Prevention
- Deep-import stage-pages/pages always
- Grep for bare package imports when the warning appears
- Enforce with lint so the wrong specifier never merges
When it happens
Trigger: Any `import ... from '@proj-airi/stage-pages'` root specifier instead of '@proj-airi/stage-pages/pages'.
Common situations: Auto-import choosing the package root; copy-pasted imports from before the entrypoint split.
Related errors
- import @proj-airi/plugin-protocol/types instead
- The entrypoint you imported for ${name} doesn't have any exp
- The file is not an AIRI Live2D motion project.
- The motion project source is invalid.
- The motion project source timeline is invalid.
AI-assisted analysis of moeru-ai/airi@677329427f (2026-08-18).
Data as JSON: /api/errors/8681df5ca02bf02d.
Report an issue: GitHub.