A Deno tool to update dependency URLs to their latest published versions with optional test validation.
deno-udd is a Deno command-line tool that automatically updates dependency URLs in Deno projects to their latest published versions. It solves the problem of manually tracking and updating dependencies by providing automated updates with optional test validation to ensure compatibility. The tool supports semantic versioning fragments to control update behavior and works with multiple Deno-compatible registries.
Deno project maintainers and developers who need to manage dependencies in Deno projects with TypeScript files. It's particularly useful for teams wanting to automate dependency updates while maintaining control over compatibility.
Developers choose deno-udd because it provides a centralized, maintainer-controlled approach to dependency updates unlike distributed systems like npm/yarn. Its unique selling point is the ability to test each dependency update before committing, ensuring stability while automating the update process.
Update Deno Dependencies - update dependency urls to their latest published versions
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Automatically updates import URLs to the latest versions from supported registries, saving manual effort as shown in the usage examples for files like deps.ts.
Optional --test flag allows running tests after each update to ensure compatibility, preventing breaking changes before committing, as highlighted in the README.
Supports version fragments like ^, ~, <, = to control update behavior, providing maintainer convenience without affecting end-users, detailed in the semantic versioning section.
Includes a scheduled GitHub Action workflow to automatically create pull requests for dependency updates, enabling continuous maintenance with minimal manual intervention.
Only works with a predefined list of registries; adding new ones requires creating an issue, which can hinder projects using custom or unsupported domains.
Installation involves running deno install with specific permissions and potentially configuring PATH, adding initial setup overhead compared to integrated tools.
Does not handle transitive dependencies or version conflicts, leaving maintainers to manually resolve issues, which can be error-prone in complex projects.