conflicted: An Alternative Conflict Resolution Strategy

R's default conflict management system gives the most recently loaded package precedence. This can make it hard to detect conflicts, particularly when they arise because a package update creates ambiguity that did not previously exist. 'conflicted' takes a different approach, making every conflict an error and forcing you to choose which function to use.

Version: 1.2.0
Depends: R (≥ 3.2)
Imports: cli (≥ 3.4.0), memoise, rlang (≥ 1.0.0)
Suggests: callr, covr, dplyr, Matrix, methods, pkgload, testthat (≥ 3.0.0), withr
Published: 2023-02-01
DOI: 10.32614/CRAN.package.conflicted
Author: Hadley Wickham [aut, cre], RStudio [cph, fnd]
Maintainer: Hadley Wickham <hadley at>
License: MIT + file LICENSE
NeedsCompilation: no
Materials: README NEWS
CRAN checks: conflicted results


Reference manual: conflicted.pdf


Package source: conflicted_1.2.0.tar.gz
Windows binaries: r-devel:, r-release:, r-oldrel:
macOS binaries: r-release (arm64): conflicted_1.2.0.tgz, r-oldrel (arm64): conflicted_1.2.0.tgz, r-release (x86_64): conflicted_1.2.0.tgz, r-oldrel (x86_64): conflicted_1.2.0.tgz
Old sources: conflicted archive

Reverse dependencies:

Reverse imports: cheem, eat, rUM, tidymodels, tidyverse, usedthese
Reverse suggests: boxr, destiny, DGEobj, DGEobj.utils, DOPE, here, marginaleffects, metaboliteIDmapping,, public.ctn0094data, SCDB, shinyTempSignal, vegawidget, vembedr, votesmart


Please use the canonical form to link to this page.