fix(bundle): do not error on failing to clean up esbuild dir#31408
fix(bundle): do not error on failing to clean up esbuild dir#31408nathanwhit merged 1 commit intodenoland:mainfrom
Conversation
WalkthroughThe change modifies the directory cleanup logic in the bundle esbuild tool. Instead of failing when directory removal encounters an error, the code now attempts removal, logs any errors as warnings, and continues execution. This makes the cleanup process non-fatal—if the directory can't be removed, the build proceeds anyway rather than halting. Estimated code review effort🎯 2 (Simple) | ⏱️ ~5–10 minutes
Pre-merge checks and finishing touches✅ Passed checks (5 passed)
✨ Finishing touches
🧪 Generate unit tests (beta)
📜 Recent review detailsConfiguration used: CodeRabbit UI Review profile: CHILL Plan: Pro 📒 Files selected for processing (1)
🧰 Additional context used📓 Path-based instructions (2)cli/tools/**/*.rs📄 CodeRabbit inference engine (CLAUDE.md)
Files:
**/*.rs📄 CodeRabbit inference engine (CLAUDE.md)
Files:
⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (8)
🔇 Additional comments (1)
Tip 📝 Customizable high-level summaries are now available in beta!You can now customize how CodeRabbit generates the high-level summary in your pull requests — including its content, structure, tone, and formatting.
Example instruction:
Note: This feature is currently in beta for Pro-tier users, and pricing will be announced later. Comment |
Fixes #31406 This is just to save some space on the user's device, no need to hard error if it fails.
…d#31408) Fixes denoland#31406 This is just to save some space on the user's device, no need to hard error if it fails.
Fixes #31406
This is just to save some space on the user's device, no need to hard error if it fails.