feat(deps): add support for Deno#10291
Conversation
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (1)
✅ Files skipped from review due to trivial changes (1)
📝 WalkthroughWalkthroughAdds Deno as a built-in dependency provider: implements ChangesDeno Dependency Provider Integration
Sequence DiagramsequenceDiagram
participant DepsEngine
participant build_provider
participant detect_applicable_providers
participant DenoDepsProvider
DepsEngine->>build_provider: Provider ID = "deno"
build_provider->>DenoDepsProvider: new(config_root, provider_config)
DenoDepsProvider-->>build_provider: DenoDepsProvider instance
DepsEngine->>detect_applicable_providers: Scan for applicable providers
detect_applicable_providers->>DenoDepsProvider: is_applicable() (checks deno.lock)
DenoDepsProvider-->>detect_applicable_providers: deno.lock exists → true
detect_applicable_providers-->>DepsEngine: [DenoDepsProvider, ...]
🎯 3 (Moderate) | ⏱️ ~20 minutes
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
Greptile SummaryThis PR adds first-class Deno support to
Confidence Score: 5/5Safe to merge — the change is additive and well isolated, with no modifications to existing provider logic. The implementation cleanly follows the established provider pattern, the e2e test exercises the full list/dry-run flow with proper cleanup, and there are no changes to existing providers or shared engine logic. src/deps/rule.rs — ordering of "deno" in BUILTIN_PROVIDERS does not match its position in detect_applicable_providers or the docs table. Important Files Changed
Reviews (3): Last reviewed commit: "Add deno do deps.md docs" | Re-trigger Greptile |
There was a problem hiding this comment.
Actionable comments posted: 2
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@src/deps/providers/deno.rs`:
- Around line 71-85: The description in add_command currently always shows "deno
install {packages}" but omits the "--dev" flag when dev is true; update the code
building the DepsCommand (in function add_command) to include "--dev" in the
description when dev is set by checking the dev boolean and prepending/inserting
"--dev" into the description string (mirror how args is constructed) so the
DepsCommand.description accurately reflects the actual program and args
(program: "deno", args, description).
- Around line 48-98: The Deno provider currently builds incorrect CLI
subcommands: change add_command to use the "add" subcommand (not "install") and
include the dev flag as Deno expects (e.g., push "--dev" or "-D" when dev is
true) and update the description to "deno add ..."; leave install_command as the
variant that runs "deno install" with no package args (used for installing from
config) and keep remove_command using "uninstall" (which matches Deno's
uninstall/remove alias) but ensure its description stays "deno uninstall ...".
Locate and edit the functions add_command, install_command, and remove_command
in the Deno provider to make these adjustments.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: defaults
Review profile: CHILL
Plan: Pro Plus
Run ID: b6c7dcb9-28de-49d0-9dc7-25dcf0d51ad9
📒 Files selected for processing (6)
e2e/cli/test_depssrc/deps/engine.rssrc/deps/mod.rssrc/deps/providers/deno.rssrc/deps/providers/mod.rssrc/deps/rule.rs
This adds support for Deno in
mise deps.Summary by CodeRabbit
New Features
Tests