dart-resolve-package-conflicts

The dart-resolve-package-conflicts skill provides a structured workflow for auditing, upgrading, and resolving dependency conflicts in Dart projects. It guides users through interpreting pub output, managing version constraints, and performing surgical updates to lockfiles.

9.2K
Installs
4
Use cases
5/10
Quality

Is dart-resolve-package-conflicts safe to install?

Review before installing

Review before installing: our audit of dart-resolve-package-conflicts's source files found 9 shell commands, 0 external URLs, file reads and writes (medium risk). Every command and URL listed appears verbatim in the skill's source. The skill requires reading and writing to pubspec.yaml and pubspec.lock files and executing Dart CLI commands.

How we audit skills: our security review methodology.

Who is this skill for?

Dart developers managing project dependencies and resolving version conflicts.

What can you do with it?

  • Auditing project dependencies for outdated packages.
  • Upgrading dependencies to resolvable versions.
  • Resolving version conflicts by surgically modifying the pubspec.lock file.
  • Tightening dependency constraints in pubspec.yaml.

How good is this skill?

Quality score: 5/10. The skill provides clear, actionable steps for common Dart dependency issues and follows best practices for lockfile management.

What does the skill file contain?

SKILL.md
# Managing Dart Dependencies

## Contents
- [Core Concepts](#core-concepts)
- [Version Constraints](#version-constraints)
- [Workflow: Auditing Dependencies](#workflow-auditing-dependencies)
- [Workflow: Upgrading Dependencies](#workflow-upgrading-dependencies)
- [Workflow: Resolving Version Conflicts](#workflow-resolving-version-conflicts)
- [Examples](#examples)

## Core Concepts

Dart enforces a strict single-version rule for dependencies: a project and all its transitive dependencies must resolve to a single, shared version of any given package. This prevents runtime type mismatches but in...

Frequently asked questions

Should I delete my pubspec.lock file to fix conflicts?

No. The skill explicitly advises against deleting the entire lockfile, as this causes uncontrolled upgrades across the dependency graph.

How do I update dependencies without changing pubspec.yaml?

Run the dart pub upgrade command to update packages to the latest version allowed by existing constraints.

What is the purpose of the --tighten flag?

The --tighten flag automatically updates the lower bounds in pubspec.yaml to match the newly resolved versions.

Data sourced from dart-lang/skills on GitHub. Install counts from skills.sh. The summary and security audit are derived from the skill's source files: every command and URL listed appears verbatim in the source.

Related skills