You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
npm run build
> [email protected] build
> next build
⚠ Invalid next.config.mjs options detected:
⚠ Unrecognized key(s) in object: 'serverComponentsExternalPackages' at "experimental"
⚠ See more info here: https://nextjs.org/docs/messages/invalid-next-config
⚠ `experimental.serverComponentsExternalPackages` has been moved to `serverExternalPackages`. Please update your next.config.mjs file accordingly.
▲ Next.js 15.1.6
- Environments: .env
Creating an optimized production build ...
✓ Compiled successfully
Linting and checking validity of types .Failed to compile.
./app/api/chat/engine/generate.ts:1:10
Type error: Module '"llamaindex"' has no exported member 'VectorStoreIndex'.
> 1 | import { VectorStoreIndex } from "llamaindex";
| ^
2 | import { storageContextFromDefaults } from "llamaindex/storage/StorageContext";
3 |
4 | import * as dotenv from "dotenv";
Static worker exited with code: 1 and signal: null
The minimum example failed with not finding the VectorStoreIndex type definition. In my actual project bootstrapped from create-llama, it also failed with not finding other definitions even after adding them with npm or pnpm
@types/llamaindex/core
@types/llamaindex/core/schema
@types/js-yaml (not relevant to this repo but same behaviour)
However, running the project in dev mode (npm run dev) is completely fine
The text was updated successfully, but these errors were encountered:
[email protected]
Next.js 15.1.6
node v23.4.0
"llamaindex": "0.8.2" (installed by create-llama)
Minimum reproducible example:
Failure message:
The minimum example failed with not finding the VectorStoreIndex type definition. In my actual project bootstrapped from
create-llama
, it also failed with not finding other definitions even after adding them withnpm
orpnpm
However, running the project in dev mode (
npm run dev
) is completely fineThe text was updated successfully, but these errors were encountered: