# Use --force-install to bypass peer dependency checks
npx opik-ts configure --force-install
```

### Package Manager Issues

If the CLI fails to detect your package manager:

1. Ensure you have a `package.json` in your project directory
2. Try running the CLI with debug mode: `npx opik-ts configure --debug`
3. Manually specify your package manager by selecting it from the prompts

### Environment Variable Setup

If environment variables aren't being set correctly:

1. Check that `.env` file was created in your project root
2. Ensure your application loads environment variables (e.g., using `dotenv`)
3. Restart your development server after running the CLI

### Integration Not Working

If traces aren't appearing in Opik:

1. Verify your `OPIK_API_KEY` is correct
2. Check that `OPIK_URL_OVERRIDE` points to the right endpoint
3. Ensure you're calling `flush()` before your application exits:
   ```typescript
   await trackedClient.flush();
   ```

### Debug Mode

Enable verbose logging to troubleshoot issues:

```bash
npx opik-ts configure --debug
```

This will show detailed information about:

* Project detection results
* Package installation steps
* File modifications
* Configuration changes

## CI/CD Integration

For automated deployments, use the non-interactive mode:

```bash