Error Messages
Miso provides clear error messages to help you understand what went wrong and how to fix it.
”miso is not currently initialized in this project”
When you see this: Miso found a lockfile or node_modules folder, but no miso.json exists.
What it means: Your project has dependencies installed, but Miso hasn’t been set up yet.
How to fix: Run miso init from the project root (where the lockfile or node_modules is located).
“no project found. miso was not able to locate a miso.json, node_modules folder, or lockfile in the parent tree”
When you see this: Miso walked up to the filesystem root without finding any project indicators.
What it means: You’re either not in a project directory, or the project hasn’t been initialized with a package manager.
How to fix:
- Navigate to your project directory
- If starting a new project, run
miso initto set up both Miso and your package manager - If in an existing project, ensure you’re in the correct directory
”package manager not configured in miso.json”
When you see this: Your miso.json exists but doesn’t have a package-manager field.
What it means: The configuration file is incomplete or corrupted.
How to fix: Edit miso.json and add a package-manager field, or delete miso.json and run miso init again.
”unsupported package manager ‘X’ specified in package.json. supported managers: [bun, npm, pnpm, yarn]”
When you see this: Your package.json has a packageManager field with an unsupported manager.
What it means: Miso doesn’t support the package manager specified in your package.json.
How to fix: Either switch to a supported manager, or manually edit miso.json after initialization to use a different manager.
”miso.json already exists”
When you see this: You tried to run miso init but miso.json already exists.
What it means: Your project is already initialized with Miso.
How to fix: If you want to reinitialize, delete miso.json first, or edit it directly to change settings.