While creating a new project with the following command:
bun create better-t-stack@latest pic-ads-saas --frontend tanstack-router --backend hono --runtime workers --api none --auth better-auth --payments polar --database sqlite --orm drizzle --db-setup d1 --package-manager bun --git --web-deploy cloudflare --server-deploy cloudflare --install --addons biome lefthook mcp turborepo --examples ai
the project scaffolding completed successfully, but dependency installation failed during the final bun install step.
Error Output
warn: incorrect peer dependency "@polar-sh/sdk@0.42.5"
error: No version matching "^3.0.3" found for specifier "@ai-sdk/react" (but package exists)
error: @ai-sdk/react@^3.0.3 failed to resolve
◇ Failed to install dependencies
ERROR Installation error: Command failed with exit code 1: bun install
Expected Behavior
The setup process should ideally continue even if dependency installation encounters an issue.
Instead of stopping the entire program immediately, it would be much better if:
- The scaffold/setup process completes fully
- Errors are collected and shown as warnings during execution
- At the end, a final summary reports:
- which dependencies failed
- what caused the issue
- suggested fixes if available
This would improve developer experience significantly, especially for large setups with many selected addons/examples.
Suggested Improvement
Please avoid making installation errors terminate the full setup process instantly.
A better UX would be:
- continue project generation
- finish all non-blocking setup steps
- show a final "Setup completed with warnings/errors" summary
This helps users avoid rerunning the entire command just because one dependency version resolution failed.
Currently, the abrupt stop makes the process feel broken even though most of the project was already scaffolded successfully.
While creating a new project with the following command:
the project scaffolding completed successfully, but dependency installation failed during the final
bun installstep.Error Output
Expected Behavior
The setup process should ideally continue even if dependency installation encounters an issue.
Instead of stopping the entire program immediately, it would be much better if:
This would improve developer experience significantly, especially for large setups with many selected addons/examples.
Suggested Improvement
Please avoid making installation errors terminate the full setup process instantly.
A better UX would be:
This helps users avoid rerunning the entire command just because one dependency version resolution failed.
Currently, the abrupt stop makes the process feel broken even though most of the project was already scaffolded successfully.