Highlights
docmd-search v0.1.6 introduces first-class support for the @docmd/engine-python engine, extending the engine resolution pipeline with a new tryImportEngine utility and expanding the fallback chain to cover Python-backed semantic indexing.
Python Engine Integration
@docmd/engine-pythonPeer Dependency: Added@docmd/engine-python >=0.8.10as an optional peer dependency. When installed alongsidedocmd-search, the Python engine is automatically detected and used for embedding generation and vector indexing.tryImportEngineUtility: Introduced a new internal resolution helper that resolves engine modules relative toprocess.cwd(), correctly handling both monorepo workspaces and standard consumer project layouts without requiring manual path configuration.- Extended Fallback Chain: The engine resolution order is now
rust → python → js → builtin, ensuring the most capable available engine is always selected automatically.
Engine API
The getEngine() factory now accepts 'python' as a valid EngineId alongside 'rust' and 'js':
import { getEngine } from 'docmd-search';
const engine = await getEngine({ engine: 'python' });
const index = await engine.buildIndex(chunks);
Plugins and integrations that previously relied on the rust or js engines can now target the Python engine explicitly, or continue to use the automatic fallback without any code changes.
Upgrade
upgrade
npm install docmd-search@0.1.6